DNS Cache, craziest thing

[oofalladeez343]

I'd go even as far as to move my desk to a galaxy far, far away... :-\ :-\ :-\ :laugh:

[Peter Kassenaar]

Pinging from The Netherlands, 2022-01-26, 08:25 UTC and got the 64.* address. Seems to be working in order, as I've never visited this address before...

[pkfox]

My ping gave **64.209.142.205** - I'm in the UK

"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP

[Alister Morton]

Just pinged 64... here in the UK.

[Clumpco]

Next time (hopefully there won't be one, but you never know) try using "nslookup" which allows you to use different name servers to see where the problem lies. By default nslookup uses your default nameserver - just type "nslookup" to start it and get the default, viz:

C:\Windows\System32>nslookup
Default Server: pi.hole
Address: 192.168.1.37

Now type in the host name that you are looking for

> www.ibm.com
Server: pi.hole
Address: 192.168.1.37

Non-authoritative answer:
Name: e7817.dscx.akamaiedge.net
Addresses: 2a02:26f0:d6:39e::1e89
2a02:26f0:d6:382::1e89
104.125.7.129
Aliases: www.ibm.com
www.ibm.com.cs186.net
outer-global-dual.ibmcom-tls12.edgekey.net

Now change the name server to see if you get the same answer.

> server 8.8.8.8
Default Server: dns.google
Address: 8.8.8.8

www.ibm.com
Server: dns.google
Address: 8.8.8.8
etc...

I hope that this helps. P.S. you will notice that I use pi-hole https://pi-hole.net/[^] , if you don't already, you should do! Kills most adverts and dodgy sites.

So old that I did my first coding in octal via switches on a DEC PDP 8

[raddevus]

Thanks for your help. I appreciate it. It looks like it finally propagated through to me too. :thumbsup:

[raddevus]

Thanks for letting me know. I appreciate it. It looks like it finally got through on my side too and I see 64.x. :thumbsup:

[raddevus]

Thanks for trying it out. I appreciate it. It seems like it finally got through to me too. :thumbsup:

[raddevus]

Very interesting and great information. This will help. Thanks for posting. :thumbsup:

[DerekT P]

I recently had some DNS issues, and my hosting provider suggested this whatsmydns.net[^] (which is possibly the most useful thing they've ever suggested :laugh: ) Easy-to-use and gives you a pretty good overview of what's happening where.

[raddevus]

very interesting. I will check it out. Thanks for posting. :thumbsup:

[danbergen]

Got 64…. With ping today 1/26/21 9:15amEST

DB

[raddevus]

Wow, that is really cool!!! :thumbsup::thumbsup:

[raddevus]

Yep, it looks like it propagated through mine too. Thanks for letting me know. Also, another user posted this fantastic service that shows dns values from around the world. it is amazing. DNS Checker - DNS Propagation Check & DNS Lookup[^]

[TNCaver]

I get the new address at 64.209.142.205.

If you think 'goto' is evil, try writing an Assembly program without JMP.

[Kirk 10389821]

Always check your DNS configuration. Also, on that machine, do nslookup host 8.8.8.8 -- A fixed name server (like one getting it correct) nslookup host -- use your default name server Doing this, you can slowly trace through every device to find it. FWIW, we have had serious delays in CABLE MODEM Country where they can take 5-7 days for some clients. And we have now started WEEKS in advance, lowering the TTL (cache time). And then making the change Friday night. 98% is all good by Sunday. But those cable companies. Anyways, this will eventually let you see who is getting it wrong. And always check the hosts files (but you know that) Finally, it sounds like you know to double check the ordering of your dns.

[raddevus]

Thanks very much. It looks like it did finally propagate through to me too. :thumbsup:

[raddevus]

Great info. Thanks for taking your time to share. I appreciate it.:thumbsup:

[Luschan]

I've got the new one (26.01.'22 21:10).