Windows – Changing DNS names on Windows Server 2008 R2

Assuming the domain in question corresponds to example.com, and that ns and ns2 are under that domain, you will also need to update the records for those entries with your domain registrar.

For example:

1. your domain is awesome.local
2. you have NS records that point to ns.awesome.local and ns2.awesome.local
3. you have A records for ns and ns2 that point to 172.27.100.10 and 172.27.100.20 (substituting your values for my arbitrary examples)

You will need to:

1. update the A records for ns and ns2 to your new IP addresses
2. update the IP address listed with your registrar to the new IP addresses (this procedure varies between registrars, but it most commonly under some kind of advanced settings section)

It's also common to lower the TTL of the records in advance so that the old records will time out from cache faster. After the migration is complete. bump them back up to your regular values. This is optional, and can sometimes help speed up the process of propagating the new records.

This is not possible by default in AWS Route 53. AWS route53 DNS servers auto generates it's DNS server list.

Read the FAQ to know more https://aws.amazon.com/route53/faqs/

There is a workaround in AWS using White label DNS server feature. See details http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/white-label-name-servers.html