On Mon, Aug 17, 2015 at 9:34 AM, MURTARI, JOHN <jm5...@att.com> wrote:
> Folks, > > > > Our normal procedure when changing the IP address of a TLD > name server is to get the new server responding properly and then update > the glue records with the Registrar to reflect the new address, normally > 1-2 days apart for two nameservers. We monitor query traffic on each and > usually see a distinctive shift once the glue record is updated and almost > all traffic shifts in the first 24 hours. e.g. > > ns1.example .com – 1.2.3.4 (first day) à > 10.20.30.40 (confirm normal ops) > > ns2.example.com—5.6.7.8 (second day) à 50.60.70.80 > > > > We had someone on staff make a suggestion we could modify > this approach by adding an additional IP address for each of the existing > servers: > > ns1.example.dom – 1.2.3.4 (first day) à 1.2.3.4 & > 10.20.30.40 (confirm normal ops) > > > > I never even thought a Registrar would allow this? Is it > supported? A useful idea in certain scenarios (although I’m not sure > when) ? > My $.02 That is a valid idea and useful. But if the NS, A, and AAAA records are approaching the max packet size, then I would avoid doing it. Also, it adds more steps to the process. So it takes a little longer but is a little less risk. Your choice. -- Bob Harold > Thanks! > > > > ---------------- > John Murtari – jm5...@att.com > > Ciberspring > > >
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
