|
|
It can take 24 to 72 hours for DNS to update across the internet.
|
|
|
|
|
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
|
|
|
|
|
There are DNS caches all around the internet; they each hold data with some expiration time.
It takes days for all of them to forget old stuff.
My ping gave 64.209.142.205
Luc Pattyn [My Articles]
The Windows 11 "taskbar" is disgusting. It should be at the left of the screen, with real icons, with text, progress, etc. They downgraded my developer PC to a bloody iPhone.
|
|
|
|
|
That's the correct one (new one). But I can't get it on my device any more. It's crazy!
I'm going to drink some coffee then hide under my desk for a while. 
|
|
|
|
|
Three days under your desk?
No, its not crazy. It is annoying, maybe very annoying, however you have to wait for all relevant nodes to have your old DNS info expired.
You might try using a VPN to some location far away, where you have never been before; and then ping again.
Luc Pattyn [My Articles]
The Windows 11 "taskbar" is disgusting. It should be at the left of the screen, with real icons, with text, progress, etc. They downgraded my developer PC to a bloody iPhone.
|
|
|
|
|
Luc Pattyn wrote: You might try using a VPN to some location far away, where you have never been before; and then ping again.
I have a DigitalOcean droplet running Debian out there on the web.
Earlier I ssh'd out to it and pinged it and it was getting 205.
I just connected to it again and I got the 64.x address.
I guess it is slowly getting propagated to DNS. Again, the weirdest thing is that this computer I'm on was getting the 64.x address & now isn't and I can't seem to get it to get back to 64.x.
Still under my desk.
|
|
|
|
|
I just hit it on the 64. address.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
Thanks very much for trying. I tried it again and I still get the 205 address.
I'm going to drink some coffee & hide under my desk for a while.
|
|
|
|
|
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...
|
|
|
|
|
Thanks for your help. I appreciate it. It looks like it finally propagated through to me too. 
|
|
|
|
|
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
|
|
|
|
|
Thanks for letting me know. I appreciate it. It looks like it finally got through on my side too and I see 64.x.
|
|
|
|
|
Just pinged 64... here in the UK.
|
|
|
|
|
Thanks for trying it out. I appreciate it. It seems like it finally got through to me too.
|
|
|
|
|
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  ) Easy-to-use and gives you a pretty good overview of what's happening where.
|
|
|
|
|
very interesting. I will check it out. Thanks for posting.
|
|
|
|
|
Wow, that is really cool!!!
|
|
|
|
|
I get the new address at 64.209.142.205.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Thanks very much. It looks like it did finally propagate through to me too.
|
|
|
|
|
I've got the new one (26.01.'22 21:10).
|
|
|
|
|
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"
|
|
|
|
|
Oh no! I'm going to be under my desk for a long, long time.
|
|
|
|
|
I'd go even as far as to move my desk to a galaxy far, far away... 
|
|
|
|
|
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.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.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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
