[87314] in North American Network Operators' Group
Re: Gothcas of changing the IP Address of an Authoritative DNS Server
daemon@ATHENA.MIT.EDU (Jason Lixfeld)
Wed Dec 14 10:25:16 2005
In-Reply-To: <1BC0CFD7-5058-494B-8969-0B54608DC631@isc.org>
From: Jason Lixfeld <jason@lixfeld.ca>
Date: Wed, 14 Dec 2005 10:19:53 -0500
To: nanog@nanog.org
Errors-To: owner-nanog@merit.edu
On 14-Dec-05, at 10:02 AM, Joe Abley wrote:
>
> You also want to check all the registries which are superordinate
> to zones your server is authoritative for, and check that any IP
> addresses stored in those registries for your nameserver are
> updated, otherwise you will experience either immediate or future
> glue madness.
>
> A conservative approach to this kind of transition is to arrange
> for your nameserver (or different nameservers hosting the same
> data) to respond on both the old and new addresses, and to continue
> in that mode until you see no queries directed at the old address
> for some safe-seeming interval (bearing in mind TTLs and cached
> records, alluded to by Steven and Sam).
If you have access customers (Dial/Broadband/etc) make sure they know
the IP for your DNS server is changing incase they hardcode IP of
your DNS server into their PCs.
