Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Troubleshooting Steps

edited January 2016 in Troubleshooting
Please use the steps below to troubleshoot any issues with the Public DNS Service.

• Verify the name you are attempting to lookup is valid and has no typos. For example, if you are using your browser to navigate to "http://www.example.com/home" ensure that the domain name (example.com in this case) is correct.

• Verify connectivity to the Verisign Public DNS servers. On a Mac or Linux machine, use the traceroute command to ensure connectivity to the servers (on a windows box, use tracert). This command will trace the network connection from your computer to the Public DNS Server.

# Linux / Mac
traceroute 64.6.64.6 -p 53 -T -n (or traceroute 64.6.65.6)
# Windows
tracert –d 64.6.64.6 (or tracert 64.6.65.6)

You should expect to see the address of the Public DNS Server (64.6.64.6 or 64.6.65.6) at the end of the list. If this is not the case, please check your network connectivity (possibly contacting your network provider)

• If your connectivity has been verified above, try to directly query the Public DNS Server.
# Linux / Mac

dig @64.6.64.6 example.com (or dig @64.6.65.6 example.com)
# Windows
nslookup example.com 64.6.64.6 (or nslookup example.com 64.6.65.6)

You should expect a result with one or more A records

Comments

  • Got servfail from the dns server
  • Hello Lalo,

    Thank you very much for your inquiry. Can you provide me with additional information regarding the error you encountered, such as the submitted query (zones queried), timestamps. The issue you are experiencing is it intermittent or consistent? Please advise

    Best Regards,

    Benjamin
    Customer Service
  • Is DNSSEC required for listing?

    I was informed that I was getting servfail because the domain was not dnssec.
  • Hello Domattps,

    DNSSEC is not required in order to be able to use the Public DNS service. We resolve signed as well as unsigned zones. If you are intending on using DNSSEC with your domain name, you will need to ensure though that your domain is properly signed since our recursive resolvers will actually validate the signing status should you have opted to use DNSSEC. If failures are detected, such as a mismatch between DS record listed in the registry and the actual signing of your zone, we will not serve up a response, which is the intended behavior for DNSSEC-aware resolvers.

    If you are running into issues with a domain which is using DNSSEC you have several free tools at your disposal that can assist you with troubleshooting, such as Verisign's DNSSEC Debugger and DNSviz just to name a few (http://dnssec-debugger.verisignlabs.com/ and http://dnsviz.net/ respectively).
  • thanks! Now I know what to check.
Sign In or Register to comment.