Filthy Earl Mooooooving

[Useless]

Well, fucking Earl and his filthy balls have still not propagated to the new host. On the other two that I had already moved (unannounced), I saw the IP change almost instantly, but Earl is stuck. If I don't see a change by this afternoon, I'm going to delete him off the current server and let that fucker 404 until the world finds its way to him. Every whois I pull shows him at his new home, but the IP I'm seeing is the old one. I haven't had this slow of a change in a couple of years. Wonder why...

[Dr Bizzaro]

You left?

[Useless]

Originally Posted by Dr Bizzaro

You left?

I've decided not to leave, but I wouldn't be surprised if I get kicked out.

[Preacher]

I doubt you'll be kicked out. It would be too noticable an absence and you are too well liked on the board. Dunno what the troubles are, but welcome back.

Oh and you are a cocksucker for never adding me to your ICQ!

[MadMax]

Originally Posted by Preacher

Oh and you are a cocksucker for never adding me to your ICQ!

Don't feel bad, he's on my contact list but he's never online anyway

[cd34]

Originally Posted by Useless Warrior

Every whois I pull shows him at his new home, but the IP I'm seeing is the old one. I haven't had this slow of a change in a couple of years. Wonder why...

The whois database is maintained separate from the root servers. So, apart from the display of the information, when you do a whois, it is totally irrelevent to when the root server update is done. Root server dns propogation is handed by your registrar. The root nameservers currently have the following info:

mcd@tsavo:~$ host -t ns filthyearl.com ns1.ucsd.edu
filthyearl.com      	NS	ns1.skilledns.info
filthyearl.com      	NS	ns2.skilledns.info

The reason that DNS may take a while to transition is that your local ISP caches the info. So, if you hit your local ISP and the root server hasn't been updated, DNS will fetch the record from the authority record. There are controls that are put on the record that give the servers information regarding cache times, etc.

			1050709647	;serial (version)
			14640	;refresh period (4 hours, 4 minutes)
			3600	;retry interval (1 hour)
			604800	;expire time (1 week)
			86400	;default ttl (1 day)
			)

here's what your record looked like when you were hosted here. Remember that caching is done per hostname, not per domain, so, it is possible that http://filthyearl.com/ would have resolved sooner if it was not cached before the root server update and that http://www.filthyearl.com/ may have still seen the old IP. 24 hours is about the max that an IP would go unchecked by any cache, however, as with any other domain, it is up to the caching resolver what to do with it for up to 7 days. Most caching resolvers only look at the TTL, but, some large providers ignore those values and use their own settings.

Your registrar updates the root servers a few times a day, so, if they do an update at 5am, and you hit the domain at 4:59am, the dns would be cached for another 24 hours by your local ISP's nameserver. Many larger registrars nowdays push root server changes every 30 minutes. Some push root server updates in realtime.

I am honored that you think highly enough of my abilities to have power over other registrars and Internet Service providers around the world, but, that's simply not the case. I wish you good luck with your new hosting and I've credited your last month's payment back to your card.

I have also changed our nameservers and pushed the updates so that the domain points to the new IP as well. If you need anything else, please feel free to ask.

If that is not what you were insinuating in your post, then you have my sincerest apologies.