Why does flush dns often fail to work?

Posted by Sharen Eayrs on Pro Webmasters See other posts from Pro Webmasters or by Sharen Eayrs
Published on 2013-10-27T02:58:41Z Indexed on 2013/10/27 4:15 UTC
Read the original article Hit count: 314

Filed under:
C:\Windows\system32>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Windows\system32>ping beautyadmired.com

Pinging beautyadmired.com [xxx.45.62.2] with 32 bytes of data:
Reply from xxx.45.62.2: bytes=32 time=253ms TTL=49
Reply from xxx.45.62.2: bytes=32 time=249ms TTL=49
Reply from xxx.45.62.2: bytes=32 time=242ms TTL=49
Reply from xxx.45.62.2: bytes=32 time=258ms TTL=49

Ping statistics for xxx.45.62.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 242ms, Maximum = 258ms, Average = 250ms

My site should point to xx.73.42.27

I change the name server. It's been 3 hours. It still points to xxx.45.62.2

Actually what happen after we change name server anyway? Wait for what? I already flush dns. Why it still points to the wrong IP?

Also most other people that do not have the DNS cache also still go to the wrong IP

© Pro Webmasters or respective owner

Related posts about dns