0

We recently switched webhosts from Databse Mart to Liquid Web. This weekend we updated the name servers with our registrar and about 48 hours later, we saw our new site on insidestl.com. Now, a day later our old site starts showing up again! Every couple of minutes the site switches. When I used http://whatsmydns.net/ it seems to have propagated to our new site.

Running ping on windows, about once a minute you can see it switches from our old ip, to our new back and forth.

Pinging insidestl.com [198.64.251.50] with 32 bytes of data:
Reply from 198.64.251.50: bytes=32 time=68ms TTL=108
Reply from 198.64.251.50: bytes=32 time=73ms TTL=108
Reply from 198.64.251.50: bytes=32 time=69ms TTL=108
Reply from 198.64.251.50: bytes=32 time=69ms TTL=108

Ping statistics for 198.64.251.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 73ms, Average = 69ms

C:\Windows\system32>ping insidestl.com

Pinging insidestl.com [198.64.251.50] with 32 bytes of data:
Reply from 198.64.251.50: bytes=32 time=68ms TTL=108
Reply from 198.64.251.50: bytes=32 time=80ms TTL=108
Reply from 198.64.251.50: bytes=32 time=81ms TTL=108
Reply from 198.64.251.50: bytes=32 time=67ms TTL=108

Ping statistics for 198.64.251.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 81ms, Average = 74ms

C:\Windows\system32>ping insidestl.com

Pinging insidestl.com [67.227.192.78] with 32 bytes of data:
Reply from 67.227.192.78: bytes=32 time=24ms TTL=50
Reply from 67.227.192.78: bytes=32 time=25ms TTL=50
Reply from 67.227.192.78: bytes=32 time=25ms TTL=50
Reply from 67.227.192.78: bytes=32 time=24ms TTL=50

Ping statistics for 67.227.192.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 25ms, Average = 24ms

C:\Windows\system32>ping insidestl.com

Pinging insidestl.com [67.227.192.78] with 32 bytes of data:
Reply from 67.227.192.78: bytes=32 time=36ms TTL=50
Reply from 67.227.192.78: bytes=32 time=23ms TTL=50
Reply from 67.227.192.78: bytes=32 time=25ms TTL=50
Reply from 67.227.192.78: bytes=32 time=25ms TTL=50

Ping statistics for 67.227.192.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 36ms, Average = 27ms

As you can see it switches back and forth between 67.227.192.78 which is the new IP and 198.64.251.50 which is our old one.

13
  • 1
    No problem found my end and tried using 3 different connections via my VPN. My guess is that your problem is local, not external. Possibly could be the DNS at your ISP playing up. You need to test it using a different ISP or a VPN. – Simon Hayter Mar 14 '16 at 18:00
  • I've done that several times. It seems to be a problem in St. Louis only.... happens on my phone's AT&T 4G, and my home's Charter internet. – Steven Landow Mar 14 '16 at 18:02
  • I'm in West County on Charter. I'll try myself. – Rob Mar 14 '16 at 18:02
  • Well its not a server issue. Its your area. – Simon Hayter Mar 14 '16 at 18:03
  • I don't see the problem either. Do you have DNS settings in your router? Charter's DNS sucks. – Rob Mar 14 '16 at 18:04
1

Notice that the ping time for the different IP addresses indicates you are being routed to different DNS servers for whatever reason. Some DNS servers take time to update though you waited 48 hours and it should have been completed by now.

I would suggest asking this question on serverfault if it doesn't resolve itself by the end of the day.

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.