Need help? Check out our Support site, then has a missing/incorrect PTR record

  1. Seems I have to pay for support now to tell you guys your site is broken, so I hope you at least check the forums.

    The DNS reverse lookup for ( is broken. This is due to a missing/incorrect PTR record. I believe it's part of an RFC spec that you must have a PTR for DNS servers. My registry ( detects that your name servers are non-compliant and says they will deregister my domain if it's not fixed in two weeks. Please fix!

    The other two name servers (ns1 and ns2) have working reverse lookup, but are technically noncompliant as well because they reference ns3 in the "additional section".

    The blog I need help with is

  2. Hey there,

    This error message occurs for some international TLDs (like .is) when an appropriate zone record has not been created for the domain. It looks like a zone record currently exists for your domain. Can you let me know if you're still having problems with your registrar?


  3. Yes it's working again. Looks like your reverse DNS was fixed. It has nothing to do with the TLD or the registrar. One of your name servers ( had a missing PTR record for itself (not my domain).

Topic Closed

This topic has been closed to new replies.

About this Topic