Important DNS Update

Setting A records for private name servers

Through its involvement in managing the root DNS servers on the net, Verisign has pushed out a change so that if private name servers are set at a registrar, then the DNS server must have a matching A record, or the site will not resolve. The way around this is simply adding an A record to the DNS zone for each name server.

To set up the A records for your private name servers:

1. Get your private name server details and their corresponding IP addresses (your A records) from your Customer Portal. 

   For example:

   • ns1.example.com (123.123.123.123)
   • ns2.example.com (50.50.50.78)
      
2. Make the necessary updates within WHM's DNS Zone Manager section. For more information on managing your private name servers within your WHM, please refer to the following article:
   • Manage DNS Zones in WHM
      
3. Ensure you enter the correct IP address per name server (NS) record. Do not interchange their IP addresses.

   For example:

   • 123.123.123.123 is only for ns1.example.com
   • 50.50.50.78 is only for ns2.example.com.
      
4. Once done, click the Save Record button.
    
5. Do NOT repeat these steps for every domain you host. This only needs to be done for your primary domain name.

Do not forget to fix your DNS Glue to ensure that your site will resolve.

What to do if the DNS records are not resolving properly?

If your sites are not resolving after adding the A records, please ensure that the private name servers are registered.

To test whether your private name servers are registered correctly, you can perform basic DNS troubleshooting or a ping test.

Please check out the following article to know what correctly configured DNS records look like and how to troubleshoot them if they're not resolving properly.

• DNS Testing and Troubleshooting Guide

If you prefer to do a ping test, see the examples below. These show how both registered and non-registered name servers appear when pinged.

Example: Ping test for a non-registered name server

The example below illustrates how the ping will look for a non-registered private name server.

C:>ping ns1.mydomain.com 
Ping request could not find host ns1.mydomain.com. Please check the name and try again.

Example: Ping test for a registered name server

The example below illustrates how the ping will look for a properly registered private name server.

C:>ping ns1.hostgator.com 

Pinging ns1.hostgator.com [67.18.54.2] with 32 bytes of data: 

Reply from 67.18.54.2: bytes=32 time=6ms TTL=56 
Reply from 67.18.54.2: bytes=32 time=6ms TTL=56 
Reply from 67.18.54.2: bytes=32 time=8ms TTL=56 
Reply from 67.18.54.2: bytes=32 time=7ms TTL=56 

Ping statistics for 67.18.54.2: 

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), 

Approximate round trip times in milli-seconds: 
    Minimum = 6ms, Maximum = 8ms, Average = 6ms 
  
C:>

Related Articles

• Do I Need a Dedicated Server?
• Do I Need a VPS?
• NVMe Dedicated Hosting Getting Started
• NVMe VPS Hosting Getting Started