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.

Joshua Walsh
  • 155
  • 10

2 Answers2

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

Amace
  • 66
  • 4
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).

bao7uo
  • 1,664
  • 11
  • 24
  • 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 00: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 00:04
  • it got the answer! – bao7uo Dec 16 '16 at 00:05
  • I used mxtoolbox too. – Joshua Walsh Dec 16 '16 at 00: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 00:07
  • @PHPaul The point is that it's a bad habit to use an ICMP echo tool to test DNS. Can it work? Sure, sometimes. Will it give you accurate results every time? No. That's why you use tools like `dig`, `nslookup`, etc. to test DNS and use `ping` to test ICMP. – EEAA Dec 16 '16 at 04:15