Propagation of DNS Changes

[Mark.Andrews at nominum.com]

	I mis-read.  That being said, all zones, except the root zone,
	have a parent zone.

	e.g.
		the parent zone of example.com is com.
		the parent zone of com is the root zone.

	And having old addresses being returned, after they should have
	expired, is often the result of having old glue in the parent
	zone.  It can also be the result of bad delegation etc.

	However since we still don't know what the domain names are and
	the problem IP addresses are or what they should be so
	providing specific help is impossible.

	Mark

> 
> While I could very easily be wrong here, I think there's some
> confusion about my "configuration".
> 
> I don't have a parent nameserver. At least, not one I'm aware of. I
> have several secondaries/slaves, and they have all been updated with
> the new/correct ftp address. I say this because the log files show the
> transfers as taking place when I restart the named demon.
> 
> Also, it wasn't the address of the >>nameserver<< I changed, it was
> the address of the box handling >>ftp<< requests.
> 
> - Mark
> 
> On 16 Oct 2000 14:48:12 -0700, Mark.Andrews at nominum.com wrote:
> 
> >
> >	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