{"id":370,"date":"2021-07-23T12:28:38","date_gmt":"2021-07-23T12:28:38","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/how-to-configure-reverse-dns-for-bind-in-whm\/"},"modified":"2021-07-23T12:28:38","modified_gmt":"2021-07-23T12:28:38","slug":"how-to-configure-reverse-dns-for-bind-in-whm","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/how-to-configure-reverse-dns-for-bind-in-whm\/","title":{"rendered":"How to Configure Reverse DNS for BIND in WHM"},"content":{"rendered":"<\/p>\n
\n
\n
\n

Valid for versions 86 through the latest version<\/em><\/p>\n<\/div>\n

\n

Version:<\/h4>\n

82<\/h4>\n

86<\/h4>\n<\/div><\/div>\n
\n

Overview<\/h2>\n

Reverse DNS uses pointer records (PTR) to convert IP addresses to domain names. Forward DNS uses A records to convert domain names to IP addresses.<\/p>\n

Mail servers use Reverse DNS information to help validate a message\u2019s source domain. System administrators use Reverse DNS information to help identify inbound connections trying to get past a firewall or other security.<\/p>\n

If your cPanel & WHM server is authoritative, you can use your DNS server to update your server\u2019s PTR records. However, most cPanel & WHM users do not<\/strong> have the authority edit their PTR record directly. Instead, some hosting providers offer reverse DNS management in a client interface. For more information, contact your hosting provider.<\/p>\n

\n
Important:<\/div>\n
\n
    \n
  • Changes to your server\u2019s DNS nameservers do not<\/strong> take effect if your server\u2019s DNS nameservers are not<\/strong> authoritative for your IP address.<\/li>\n
  • Many hosting providers do not allow their customers to modify their nameserver PTR records. Contact your hosting provider to delegate authority to your nameservers or set up your nameserver PTR records.<\/li>\n
  • If you are updating PTR records for mail purposes, it is only necessary to update the records for IP addresses that your sites use to send mail.<\/li>\n<\/ul><\/div>\n<\/div>\n

    Configure reverse DNS<\/h2>\n
    \n
    Note:<\/div>\n
    \n

    In the following examples:<\/p>\n

      \n
    • example.com<\/code> represents your domain.<\/li>\n
    • 192.168.0.1<\/code> represents your main IP address.<\/li>\n
    • 0.168.192.in-addr.arpa<\/code> represents your your server\u2019s main IP address, in PTR record format.<\/li>\n<\/ul><\/div>\n<\/div>\n

      Use the following steps to configure your server\u2019s authoritative nameservers:<\/p>\n

      System requirements<\/h3>\n

      PTR records require<\/strong> authoritative DNS nameservers before they can function properly. To find the authoritative DNS nameservers of your server\u2019s main IP address, trace the Start Of Authority (SOA) record. To do this, run the following command:<\/p>\n

      \n
      dig +nssearch 0<\/span>.168.192.in-addr.arpa<\/code><\/pre>\n<\/div>\n
      Add the reverse DNS zone<\/h3>\n
      Navigate to WHM\u2019s Add a DNS Zone<\/em> interface (WHM >> Home >> DNS Functions >> Add a DNS Zone<\/em>) and enter the following information:<\/p>\n
      \n
      Note:<\/div>\n
      \n
        \n
      • This interface does not<\/strong> currently support IPv6.<\/li>\n
      • If your hosting provider delegates you a byte boundary that is greater<\/strong> than 25<\/code>, separate the network range and byte boundary with a dash (\u2013<\/code>) character. Do not<\/strong> use a forward slash (\/<\/code>) character. For example,\n
        \n
        128<\/span>-24.0.168.192.in-addr.arpa\n<\/code><\/pre>\n<\/div>\n
        For more information, read the RFC 2317 documentation.<\/li>\n<\/ul><\/div>\n<\/div>\n
          \n
        1. Enter your server\u2019s IP address in the IPv4 Address<\/em> text box.<\/li>\n
        2. Enter the reverse DNS zone\u2019s name in the Domain<\/em> text box.<\/li>\n
        3. Create a reverse DNS zone name for an IPv4 address. To do this, perform the following steps:\n
            \n
          1. Drop the last octet from the IP address.<\/li>\n
          2. Reverse the order of the remaining octets.<\/li>\n
          3. Append .in-addr.arpa<\/code> to the end of the octets.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
            A complete reverse DNS zone name for an IPv4 address will resemble the following example:<\/p>\n
            \n
            128<\/span>\/24.0.168.192.in-addr.arpa<\/code><\/pre>\n<\/div>\n
            Edit the reverse DNS zone file<\/h3>\n
            After creating your zone file, create the reverse DNS zone file\u2019s PTR record in WHM\u2019s DNS Zone Manager<\/em> interface (WHM >> Home >> DNS Functions >> DNS Zone Manager<\/em>).<\/p>\n
            \n
            Note:<\/div>\n
            \n
            Your zone file already contains a Nameserver (NS) record for each of your server\u2019s authoritative nameservers.<\/p>\n<\/p><\/div>\n<\/div>\n
            To add the DNS zone\u2019s PTR record, perform the following steps:<\/p>\n
              \n
            1. In WHM\u2019s DNS Zone Manager<\/em> interface, click Manage<\/em> next to the domain you want to modify. The system will direct you an interface that displays the domain\u2019s current list of zone records.<\/li>\n
            2. Click Add Record<\/em>. The system will create a new record entry row in the table.<\/li>\n
            3. Select PTR<\/em> from the Type<\/em> menu.<\/li>\n
            4. Enter the DNS zone record\u2019s information in the text boxes, then click Add Record<\/em>.<\/li>\n<\/ol>\n
              Test your records<\/h3>\n
              After your domain\u2019s DNS information propagates, confirm that you properly configured reverse DNS. To confirm that you properly configured reverse DNS, run the following command:<\/p>\n
              \n
              host 192<\/span>.168.0.1<\/code><\/pre>\n<\/div>\n
              If you correctly configured reverse DNS, the output will resemble the following example:<\/p>\n
              \n
              1<\/span>.0.168.192.in-addr.arpa domain name pointer www.example.com.<\/code><\/pre>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"
              Valid for versions 86 through the latest version Version: 82 86 Overview Reverse DNS uses pointer records (PTR) to convert IP addresses to domain names. Forward DNS uses A records to convert domain names to IP addresses. Mail servers use Reverse DNS information to help validate a message\u2019s source domain. System administrators use Reverse DNS …<\/p>\n","protected":false},"author":1,"featured_media":371,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/370"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=370"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/370\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/371"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=370"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=370"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=370"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}