Propagation of DNS Changes

[Mark.Andrews at nominum.com]

	Mathias gave you some causes, but as this is the address of
	a nameserver dis you remember to inform the parent zone of
	the new IP address of the nameserver?  The parent zone has
	its own copy of the record so that the DNS doesn't get into
	a catch 22 of "need to have the address of the nameserver to
	get the address of the nameserver".

	Mark

> 
> I'm confused about how DNS changes propagate thru the internet and
> hope someone here can un-confuse me...
> 
> I recently discovered an error in the DNS on my server (which is the
> master for my ip domain) that involved the A record for my ftp.
> 
> I corrected this, and restarted named (8.2.2-p5), only to remember I
> had forgotten to update the date+serial number.
> 
> So I went back in, changed the date+serial #, and restarted named.
> 
> This last step happened several days ago. However, when I do an
> nslookup on my backup ISP account (earthlink.net), ftp resolves to my
> primary ip address, rather than the hosting service I use. If I do the
> nslookup but require the use of my own server, I get the correct
> answer (i.e., ftp maps to the ftp hosting service).
> 
> Have I screwed something up here by "iterating" the DNS changes and
> neglecting to update the date+serial # info until the very end? If so,
> how do I fix it?
> 
> Thanx in advance for any help and/or advice!
> 
> - Mark
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com