[87277] in North American Network Operators' Group
Re: Gothcas of changing the IP Address of an Authoritative DNS Server
daemon@ATHENA.MIT.EDU (Sam Crooks)
Tue Dec 13 16:13:31 2005
Date: Tue, 13 Dec 2005 14:12:17 -0700
From: Sam Crooks <anti.confidentiality.notices@gmail.com>
To: Eric Kagan <ekagan@axsne.com>, nanog@merit.edu,
nanog-post@merit.edu
In-Reply-To: <03c901c60026$20232810$660da8c0@axsdom.local>
Errors-To: owner-nanog@merit.edu
I would think you would want to drop your DNS record TTLs for all
domains being moved to something very low several days before the
switch-over period.
On 12/13/05, Eric Kagan <ekagan@axsne.com> wrote:
>
> We need to move our Primary DNS server from legacy IP space provided by o=
ur
> upstreams to our ARIN Assigned IP space. I am looking for advice and any
> gotchas. I couldn't find any white papers to this affect or archived
> articles or postings. If someone does have a resource for this or find t=
his
> could be valuable, I can certainly gather all the info and document it.
> Most of the Registrars I have seen now use the Authoritative DNS Server H=
ost
> names for the domain name registrations vs the IP Address. For most of ou=
r
> customers, we register and host the DNS. I have confirmed almost all the
> customers have either Network Solutions, Tucows, Go Daddy and Register.co=
m.
>
> Can I simply change the IP address of our DNS server and update the DNS H=
ost
> Record with our registrar with the new IP and any A / NS records we have =
?
> As long as other customers domains have our DNS Server FQDN as the Host,
> they should not need to make any changes, correct ? I would love to thi=
nk
> its that simple, but there is always a gotcha. Does anyone know of any m=
ain
> registries using just the IP Address where the customer might need to go =
in
> and make those changes for each and every domain ? Any input, advice or
> ideas is appreciated.
>
> Thanks
> Eric
>
