Name Server Migration FAQ

Topics

1. Your name server segment
2. Why there is no service interruption when migrating name servers
3. How to migrate to the new name servers
4. How to test <Name Server Segment> before migration. (This is not necessary but can provide confidence.)
5. How to know when registrar has updated name servers
6. How to test <Name Server Segment> after registrar update

Name Server Segment

<Name Server 1. IPv4 Address IPv6 Address>
<Name Server 2. IPv4 Address IPv6 Address>
<Name Server 3. IPv4 Address IPv6 Address>
<Name Server 4. IPv4 Address IPv6 Address>

Why There Is No Service Interruption when Migrating Name Servers

All of your DNS data is on both Pdns1-6 segment and <Name Server Segment> and will remain that way before, during and after migration.  These name server segments have synchronized data as they are fed by the same databases.  That means that no matter which of these name servers you are pointing to, your domains  will still resolve.

How to Migrate to New Name Servers

Let us know if you wish to migrate all domains at once or a few initially and at what time.  Whichever approach you take, your domains will still be available to resolve from both segments. At that time, we will update the NS records in your zone files. Afterwards you’ll need to contact your registrar for those domains and update your authoritative name servers to these:

<Name Server 1.>
<Name Server 2.>
<Name Server 3.>
<Name Server 4.>

How to Test <Name Server Segment> Before Migration

You can test directly to <Name Server Segment> from several DNS testing websites using:

http://www.digwebinterface.com/

1. Enter the list of hosts you wish to test under “Hostnames or IP addresses:”
2. Select “Specify myself:” under Nameservers and enter the name servers below:
3. Click "Dig"

<Name Server 1.>
<Name Server 2.>
<Name Server 3.>
<Name Server 4.>

How to Know When Registrar Has Updated Name Servers

Your registrar will give you a time estimate on when your authoritative name servers will be updated, but they may not give an exact time. You can test with this link:

http://www.digwebinterface.com/?hostnames=imf.org&type=&trace=on&ns=resolver&useresolver=8.8.4.4&nameservers=

1. Enter the list of hosts you wish to test under “Hostnames or IP addresses:”
2. Select Resolver under “Name Servers:”
3. Check Trace under “Options”
4. Click Dig

How to Test <Name Server Segment> after Registrar Update

You can test it in two ways now, authoritatively and recursively. Authoritative test is the same as before using http://www.digwebinterface.com/.

1. Enter the list of hosts you wish to test under “Hostnames or IP addresses:”
   
2. Select “Specify myself:” under Nameservers and enter these name servers below.
3. Click “Dig”

<Name Server 1.>
<Name Server 2.>
<Name Server 3.>
<Name Server 4.>

Recursive test is subject to caching and may continue to show PDNS1-6 answers for up to a day after your change:

http://www.digwebinterface.com/?hostnames=imf.org&type=&useresolver=8.8.4.4&ns=all&nameservers=

1. Enter the list of hosts you wish to test under “Hostnames or IP addresses:”
2. Select “All:” under Nameservers
3. Click “Dig”

This test goes out to various recursive servers throughout the Internet and shows current results.  The TTL’s might have differing values because records are cached at different times and have different remaining durations.  Let us know if you have any questions.

Additional Information

UltraDNS name servers are each treated equal in 2024. Topologically speaking, BGP anycast and client/intermediary ISP routing tables insure that a query will go to the "best available" name server for resolution. If there is an issue at one of our node locations, then the announcement is taken down, and queries go to the "next best". Each node answers for ALL UltraDNS name servers with as many as five upstream ISPs (depending on local availability). Use whichever set you prefer.