There was a problem loading the comments.

Important DNS Update

Support Portal  »  Knowledgebase  »  Viewing Article


Verisign (through their involvement in the management of the root DNS servers on the net) has pushed out a change so if you have private nameservers set at your registrar, then your DNS server must have a matching A record or the site will not resolve. The way around this is to simply add an A record to the DNS zone for each nameserver.

Note, this should only concern anyone using private nameservers. Hatchling, Baby, and Business plan owners should not worry about this, as they cannot use private name servers.

Creating the A records

  1. Login to WHM and look under DNS Functions.
  2. Click Edit DNS Zone and select the primary domain (the one that appears in your welcome email).
  3. Click the Edit button and wait for the page to load.
  4. Check your New Account Info email for the correct name server IPs.
    • ->
    • ->
    (If you only have one IP, the second IP is the first IP +1 to the last number, e.g.
  5. This is exactly the information you need for the record name and address. Almost done!
  6. Back at WHM, scroll down to where you see "Add New Entries Below this Line".
  7. In the first blank below that line, type ns1
  8. Skip the 14400, and in the drop down select "A".
  9. A new box will appear. Erase "IP or Hostname" and type your NS1 IP address. EXAMPLE:
  10. In the second blank below that line, type ns2
  11. Skip the 14400, and in the drop down select "A".
  12. A new box will appear. Erase "IP or Hostname" and type your NS2 IP address. EXAMPLE:
  13. Scroll all the way down and click the Save button.

When you get to the last step, it should look similar to this screen shot.

Do NOT repeat for every domain you host. This only needs to be done for your primary domain name.

Be sure to also fix your DNS glue (see Related Article).

If this does not fix your problem, then please make sure that you have registered your private nameservers first. To test if your private nameservers are correctly registered, you can ping each name.

Here I show an example of a nameserver which is not registered (, and then one that is registered (


Ping request could not find host Please check the name and try again.



Pinging [] with 32 bytes of data:

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

Ping statistics for
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 8ms, Average = 6ms


Share via
Did you find this article useful?  

Related Articles


Add Comment

Replying to  

© Osirion System Technologies