DNS Answer, Part III -- Case-in-point

[Benjamin Scott]

On Aug 17 at 12:38pm, Cole Tuininga wrote:
> I thought it was as simple as changing the A records for ns[12] to the new 
> IPs and wait for it to propagate.

   Changing the A records where?  If you only updated your local zone file, you 
need to submit changes to the registrar.  Or vice versa.

> I did this several days ago (TTL, etc is set for a mere 3 hours for the 
> domain) ...

   This isn't the only thing that matters, because the delegation from the TLD 
has a 48 hour TTL.  There are also additional processing delays before changes 
you submit become visible to the world.  So some people may still be asking 
old servers, even if your domain records have low TTLs.  Of course, if they 
reach your servers and get updated records, that may work out.

> egon at trogdor:~$ host ns1.code-energy.com
> ns1.code-energy.com has address 208.3.246.215

   As of 11:00 PM EDT, Wed 17 Aug 2005, I am seeing the following:

 	code-energy.com.       NS   ns1.code-energy.com.
 	code-energy.com.       NS   ns2.code-energy.com.
 	ns1.code-energy.com.   A    64.34.179.90
 	ns2.code-energy.com.   A    64.34.182.198

I get that answer from <a.gtld-servers.net>, as well as all four of the IP 
addresses you mentioned.  So it appears you are internally and externally 
consistent, and all changes have propagated within the delegation path.

   Again, some ISPs may override TTL.

   Hope this helps,

-- 
Ben <dragonhawk at iname.com>