DNS Cache, craziest thing
-
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.
-
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