Why flush dns often doesn't work

1

After we change name server we often want to see how our new site look like.

Sometimes the name server hasn't propagated properly to our site.

So we flush dns.

It doesn't work. It never work

C:\Users\jim2>ping goldslady.com

Pinging goldslady.com [50.87.145.204] with 32 bytes of data:
Reply from 50.87.145.204: bytes=32 time=220ms TTL=51
Reply from 50.87.145.204: bytes=32 time=213ms TTL=49
Reply from 50.87.145.204: bytes=32 time=213ms TTL=51
Reply from 50.87.145.204: bytes=32 time=211ms TTL=49

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

C:\Users\jim2>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Users\jim2>ping goldslady.com

Pinging goldslady.com [50.87.145.204] with 32 bytes of data:
Reply from 50.87.145.204: bytes=32 time=225ms TTL=51
Reply from 50.87.145.204: bytes=32 time=207ms TTL=49
Reply from 50.87.145.204: bytes=32 time=214ms TTL=49
Reply from 50.87.145.204: bytes=32 time=205ms TTL=49

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

C:\Users\jim2>

user4951

Posted 2013-07-23T00:15:12.643

Reputation: 3 015

Answers

2

When you flush your DNS, you are only invalidating your local cache for name resolving. You are still being fed old results because your ISP caches DNS records as well. In order to see the actual changes you must either:

  • wait until the TTL (time to live) specified in your DNS entry expires, OR
  • force a local change using the hosts file (in that case you might be the only one able to access the live site just yet)

Debugging live DNS queries

For a service that directly queries the name servers, without using any cache, visit: http://www.dnswatch.info/

There you can see the route it does to reach to your A record (or other types).

Another useful tool in cmd you can use is nslookup. In your case:

nslookup -type=A goldslady.com 8.8.8.8

will yeld results using the Google Public DNS server.

Hope it helps!

rodolfo42

Posted 2013-07-23T00:15:12.643

Reputation: 36

Could you explain what nslookup -type=A goldslady.com 8.8.8.8 really does? And how is it connected with Google Public DNS Server – Mahdi Alkhatib – 2018-04-17T13:52:38.510

1@MahdiAlkhatib this command issues a request to translate the domain "goldslady.com" into an IPv4 adress ("-type=A") using the Google Public DNS Server, which is accessed using the 8.8.8.8 IP address. In case you're wondering, it does not change any DNS records or flushes any cache anywhere. – rodolfo42 – 2018-04-18T09:53:13.443

But it should update the DNS of company's local server as it sees there is a new DNS for this request domain name. – Mahdi Alkhatib – 2018-04-18T11:12:50.700

Where is this TTL show? HOw do I speed things up? – user4951 – 2013-07-23T00:59:58.407

@JimThio It's right where you configured your domain to point to the new IP, with your domain registrar (ex: GoDaddy.com) or a delegated DNS server provider. Looking at your domain goldslady.com it seems your DNS server is buildingsuperteams.com - look here

– None – 2013-07-23T13:56:44.230