Thursday, June 23, 2016

Altering names for DNS servers where Primary and Parent records may not be changed at the same time

I have a few Name Servers (BIND9) that I want to alter the Fully Qualified Name for. As a hypothetical example:




  • dns1.olddomain.com

  • dns2.olddomain.com

  • dns3.olddomain.com



Are the old Name Servers and I would like to use the following instead.





  • dns1.newdomain.com

  • dns2.newdomain.com

  • dns3.newdomain.com



Presently all of the above records point to the same DNS servers, but the IP's of the new are different then the old (they route into the same machines).



My question here is if I update all the zones on my servers to use the new names for the SOA and NS, will I run into any issues if people using these servers do not update the registration records right away? Or will they have an issue is they jump the gun and update the registration prior to my change?




I have done several tests resolving records using both scenarios, and so far I don't see that there is an issue with resolution. However I am unsure if there is something I am missing here.

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...