1. Knowledge Base
  2. >
  3. Results
  4. >
  5. Important DNS Update

Important DNS Update

 

Step 2 of 3 of setting up private name servers.


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.

Note: This should only concern anyone using private name servers. Shared hosting (Hatchling, Baby, and Business) plan owners should not worry about this since they cannot use private name servers.

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

  1. Get your private name server details. Your Customer Portal and HostGator Welcome email will provide you with information about your private name servers and their corresponding IP addresses (your A records). 

    For example:

    • ns1.hgexample.com (123.123.123.123)
    • ns2.hgexample.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:
  3. Ensure that you're entering the correct IP address per nameserver (NS) record. Do not interchange their IP addresses.

    For example:

    • 123.123.123.123 is only for ns1.hgexample.com
    • 50.50.50.78 is only for ns2.hgexample.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.
  6. Be sure also to fix your DNS Glue to ensure that your site will resolve. If your DNS records are not resolving properly, proceed to the next section.

Troubleshooting and confirming settings

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

To test if your private name servers are registered correctly, you can do some basic DNS troubleshooting, or you can also do 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.

If you prefer doing 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:>