0

My VPS host recently suspended my service because my site was under a DDoS attack. When they brought me back online, my IP had changed. I can now only view my site by requesting it's IP http://176.126.69.72/, not using the domain name http://gatewaygaming.net.au/.

I've updated my A records and verified that when I enter the domain name my computer is indeed trying to connect to the right server. Weirdly, if I execute "wget http://gatewaygaming.net.au/" on the server itself I can view the page.

  • 1
    What happens when you use the domain? – EEAA Dec 15 '16 at 23:58
  • Good question, it sticks on "waiting for gatewaygaming.net.au" and eventually times out. – Joshua Walsh Dec 15 '16 at 23:59
  • Further info: No connection attempt is logged in access_log or error_log, so I think the issue isn't apache. I'm not sure what it could be though. – Joshua Walsh Dec 16 '16 at 0:01
  • What does that dns record resolve to locally on your client? – EEAA Dec 16 '16 at 0:03
2

Looks like you made a typo when you updated the A Record. When I pinged that domain name the IP I got is: 172.126.69.72 not 176.126.69.72

  • nice one @amace :) – bao7uo Dec 16 '16 at 0:06
  • I have done this before myself.... 172 is also a subnet octet I am use to typing. – Amace Dec 16 '16 at 0:07
  • I wasn't able to accept it at the time because Serverfault has a minimum time before you can accept an answer. It's accepted now though, thanks so much for finding my mistake! – Joshua Walsh Dec 16 '16 at 0:58
0

Type ping gatewaygaming.net.au on the server itself, and see if the IP that comes up is the new one - don't think it will be.

Check your apache config to make sure that the server is configured to listen on the new IP, and that the associated hostname is configured as a virtual host on the new IP (if necessary).

  • The IP that shows up in this case is 127.0.0.1. The server is definitely listening on that IP, and I'm not using virtualhosts. – Joshua Walsh Dec 16 '16 at 0:04
  • Don't use ping to diagnose DNS, for pete's sake. Use a dns tool. Using ping can result in unreliable results. – EEAA Dec 16 '16 at 0:04
  • it got the answer! – bao7uo Dec 16 '16 at 0:05
  • I used mxtoolbox too. – Joshua Walsh Dec 16 '16 at 0:06
  • anyway so 127.0.0.1 is why it was connecting on the server itself, and amace has got you the solution – bao7uo Dec 16 '16 at 0:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.