DNS Cache, craziest thing
-
So i'm switching to a new WebHost. I switched my DNS hosts to the new ones (in Google Domains) and waited. That worked fine after a wait and my new ip address came up. 65.x.x.x Hours later I'm working on my web site and something odd happens I see the old web site. I ping the site from the same machine where i saw it change to 65.x.x.x (new ip address). It is now pointing back to old one 205.x.x.x :confused: :wtf: No idea. I've flushed local cache etc. Still old one now. I went to my DigitalOcean site and pinged it got 205.x.x.x (OLD ONE!!!) Went to another computer on another network and pinged I get the new one 65.x.x.x. Wha?t!?? :confused: :wtf: :confused: :wtf: :confused: :wtf: :confused: Really exasperating. ## UPDATE ## Problem still occuring. I thought of something: Test on my phone (with wifi turned off -- using cellular data). 1. turned off wifi on my phone and hit newlibre.com -- saw my new web site. 2. turned wifi back on (on phone) and navigated to newlibre.com -- saw the old site. 3. obviously this is cached on my wifi router, right? 4. Imma haf to reboot my wifi router I guess. OY!!! ### UPDATE 2 #### I fired up a Win10 image via VirtualBox and ran ipconfig /flushdns All of a sudden I saw the new IP Address. VirtualBox win10 was running under this Linux machine I'm on. Finally saw the correct IP address here too. I guess it just propagated through, because I never did reboot the wifi router. I've finally crawled back out from under my desk. :rolleyes:
Many years ago, I posted another weird DNS oddity...another domain name was pointed to my address. Even after I redirected to a custom page 'hey, check your DNS settings...' it stayed that way for several years until the webhost upgraded.
"Go forth into the source" - Neal Morse "Hope is contagious"
-
Many years ago, I posted another weird DNS oddity...another domain name was pointed to my address. Even after I redirected to a custom page 'hey, check your DNS settings...' it stayed that way for several years until the webhost upgraded.
"Go forth into the source" - Neal Morse "Hope is contagious"
-
I'd go even as far as to move my desk to a galaxy far, far away... :-\ :-\ :-\ :laugh:
-
Yeah, I do believe that. The odd thing is that this computer had connected to the correct ip address earlier today. Now I cannot get it to get that ip address again. I've flushed dns multiple times, etc. It's crazy. and yet, my work network thinks it has the new IP address & I even ran ipconfig / flushdns there and it still has the new IP address. Let's see what people get: $ ping newlibre.com The old one is : 205.144.171.178 The new one is (note - I thought it was 65.x but is different): 64.209.142.205 Ping and reply if you don't mind. I'm just interested. Thanks
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...
-
Yeah, I do believe that. The odd thing is that this computer had connected to the correct ip address earlier today. Now I cannot get it to get that ip address again. I've flushed dns multiple times, etc. It's crazy. and yet, my work network thinks it has the new IP address & I even ran ipconfig / flushdns there and it still has the new IP address. Let's see what people get: $ ping newlibre.com The old one is : 205.144.171.178 The new one is (note - I thought it was 65.x but is different): 64.209.142.205 Ping and reply if you don't mind. I'm just interested. Thanks
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
-
Yeah, I do believe that. The odd thing is that this computer had connected to the correct ip address earlier today. Now I cannot get it to get that ip address again. I've flushed dns multiple times, etc. It's crazy. and yet, my work network thinks it has the new IP address & I even ran ipconfig / flushdns there and it still has the new IP address. Let's see what people get: $ ping newlibre.com The old one is : 205.144.171.178 The new one is (note - I thought it was 65.x but is different): 64.209.142.205 Ping and reply if you don't mind. I'm just interested. Thanks
Just pinged 64... here in the UK.
-
So i'm switching to a new WebHost. I switched my DNS hosts to the new ones (in Google Domains) and waited. That worked fine after a wait and my new ip address came up. 65.x.x.x Hours later I'm working on my web site and something odd happens I see the old web site. I ping the site from the same machine where i saw it change to 65.x.x.x (new ip address). It is now pointing back to old one 205.x.x.x :confused: :wtf: No idea. I've flushed local cache etc. Still old one now. I went to my DigitalOcean site and pinged it got 205.x.x.x (OLD ONE!!!) Went to another computer on another network and pinged I get the new one 65.x.x.x. Wha?t!?? :confused: :wtf: :confused: :wtf: :confused: :wtf: :confused: Really exasperating. ## UPDATE ## Problem still occuring. I thought of something: Test on my phone (with wifi turned off -- using cellular data). 1. turned off wifi on my phone and hit newlibre.com -- saw my new web site. 2. turned wifi back on (on phone) and navigated to newlibre.com -- saw the old site. 3. obviously this is cached on my wifi router, right? 4. Imma haf to reboot my wifi router I guess. OY!!! ### UPDATE 2 #### I fired up a Win10 image via VirtualBox and ran ipconfig /flushdns All of a sudden I saw the new IP Address. VirtualBox win10 was running under this Linux machine I'm on. Finally saw the correct IP address here too. I guess it just propagated through, because I never did reboot the wifi router. I've finally crawled back out from under my desk. :rolleyes:
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.37Now type in the host name that you are looking for
> www.ibm.com
Server: pi.hole
Address: 192.168.1.37Non-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.netNow 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.8www.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
-
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...
-
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
-
Just pinged 64... here in the UK.
-
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.37Now type in the host name that you are looking for
> www.ibm.com
Server: pi.hole
Address: 192.168.1.37Non-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.netNow 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.8www.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
-
Yeah, I do believe that. The odd thing is that this computer had connected to the correct ip address earlier today. Now I cannot get it to get that ip address again. I've flushed dns multiple times, etc. It's crazy. and yet, my work network thinks it has the new IP address & I even ran ipconfig / flushdns there and it still has the new IP address. Let's see what people get: $ ping newlibre.com The old one is : 205.144.171.178 The new one is (note - I thought it was 65.x but is different): 64.209.142.205 Ping and reply if you don't mind. I'm just interested. Thanks
-
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.
-
So i'm switching to a new WebHost. I switched my DNS hosts to the new ones (in Google Domains) and waited. That worked fine after a wait and my new ip address came up. 65.x.x.x Hours later I'm working on my web site and something odd happens I see the old web site. I ping the site from the same machine where i saw it change to 65.x.x.x (new ip address). It is now pointing back to old one 205.x.x.x :confused: :wtf: No idea. I've flushed local cache etc. Still old one now. I went to my DigitalOcean site and pinged it got 205.x.x.x (OLD ONE!!!) Went to another computer on another network and pinged I get the new one 65.x.x.x. Wha?t!?? :confused: :wtf: :confused: :wtf: :confused: :wtf: :confused: Really exasperating. ## UPDATE ## Problem still occuring. I thought of something: Test on my phone (with wifi turned off -- using cellular data). 1. turned off wifi on my phone and hit newlibre.com -- saw my new web site. 2. turned wifi back on (on phone) and navigated to newlibre.com -- saw the old site. 3. obviously this is cached on my wifi router, right? 4. Imma haf to reboot my wifi router I guess. OY!!! ### UPDATE 2 #### I fired up a Win10 image via VirtualBox and ran ipconfig /flushdns All of a sudden I saw the new IP Address. VirtualBox win10 was running under this Linux machine I'm on. Finally saw the correct IP address here too. I guess it just propagated through, because I never did reboot the wifi router. I've finally crawled back out from under my desk. :rolleyes:
-
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.
-
Yeah, I do believe that. The odd thing is that this computer had connected to the correct ip address earlier today. Now I cannot get it to get that ip address again. I've flushed dns multiple times, etc. It's crazy. and yet, my work network thinks it has the new IP address & I even ran ipconfig / flushdns there and it still has the new IP address. Let's see what people get: $ ping newlibre.com The old one is : 205.144.171.178 The new one is (note - I thought it was 65.x but is different): 64.209.142.205 Ping and reply if you don't mind. I'm just interested. Thanks
-
So i'm switching to a new WebHost. I switched my DNS hosts to the new ones (in Google Domains) and waited. That worked fine after a wait and my new ip address came up. 65.x.x.x Hours later I'm working on my web site and something odd happens I see the old web site. I ping the site from the same machine where i saw it change to 65.x.x.x (new ip address). It is now pointing back to old one 205.x.x.x :confused: :wtf: No idea. I've flushed local cache etc. Still old one now. I went to my DigitalOcean site and pinged it got 205.x.x.x (OLD ONE!!!) Went to another computer on another network and pinged I get the new one 65.x.x.x. Wha?t!?? :confused: :wtf: :confused: :wtf: :confused: :wtf: :confused: Really exasperating. ## UPDATE ## Problem still occuring. I thought of something: Test on my phone (with wifi turned off -- using cellular data). 1. turned off wifi on my phone and hit newlibre.com -- saw my new web site. 2. turned wifi back on (on phone) and navigated to newlibre.com -- saw the old site. 3. obviously this is cached on my wifi router, right? 4. Imma haf to reboot my wifi router I guess. OY!!! ### UPDATE 2 #### I fired up a Win10 image via VirtualBox and ran ipconfig /flushdns All of a sudden I saw the new IP Address. VirtualBox win10 was running under this Linux machine I'm on. Finally saw the correct IP address here too. I guess it just propagated through, because I never did reboot the wifi router. I've finally crawled back out from under my desk. :rolleyes:
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.
-
I get the new address at 64.209.142.205.
If you think 'goto' is evil, try writing an Assembly program without JMP.
-
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.
