{"id":946,"date":"2021-07-23T12:41:49","date_gmt":"2021-07-23T12:41:49","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/edit-dns-zone\/"},"modified":"2021-07-23T12:41:49","modified_gmt":"2021-07-23T12:41:49","slug":"edit-dns-zone","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/edit-dns-zone\/","title":{"rendered":"Edit DNS Zone"},"content":{"rendered":"<\/p>\n
\n
\n
\n

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

\n

Version:<\/h4>\n

82<\/h4>\n

86<\/h4>\n

88<\/h4>\n<\/div><\/div>\n
\n

Overview<\/h2>\n

This feature allows you to edit the records in a domain\u2019s DNS zone file.<\/p>\n

\n
Warning:<\/div>\n
\n
    \n
  • \n

    We removed<\/strong> this interface in cPanel & WHM version 96. Use WHM\u2019s DNS Zone Manager<\/em> interface (WHM >> Home >> DNS Functions >> DNS Zone Manager<\/em>). For more information, read our cPanel Deprecation Plan documentation.<\/p>\n<\/li>\n

  • \n

    We deprecated<\/strong> the MyDNS and NSD nameserver software in cPanel & WHM version 78 and plan to remove them in a future release. If you use either of these nameservers, we strongly<\/strong> recommend that you migrate to either the PowerDNS or BIND namesevers. For more information, read our cPanel Deprecation Plan documentation.<\/p>\n<\/li>\n

  • \n

    You must<\/strong> configure your DNS records correctly to allow visitors to access the domains.<\/p>\n<\/li>\n

  • \n

    DNS zones that reside on other Write-only<\/em> DNS servers in a DNS cluster do not<\/strong> appear in this interface.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n

    To edit a DNS zone or view zone information, select the desired domain from the Choose a Zone<\/em> to Edit menu and click Edit<\/em>. A new interface will appear.<\/p>\n

    Zone and server information<\/h2>\n

    The top of the Edit DNS Zone<\/em> interface displays the following zone and server information:<\/p>\n

      \n
    • cPanel first<\/em> \u2014 The cPanel & WHM version and build number on which you created the DNS zone.<\/li>\n
    • update_time<\/em> \u2014 The Unix date and time of the last update to the zone file.<\/li>\n
    • Cpanel::ZoneFile::VERSION<\/em> \u2014 The zone file version that cPanel & WHM uses.<\/li>\n
    • hostname<\/em> \u2014 The server\u2019s hostname.<\/li>\n
    • latest<\/em> \u2014 The current cPanel & WHM version on the server.<\/li>\n
    • Zone file for<\/em> \u2014 The DNS zone\u2019s domain.<\/li>\n
    • $TTL<\/em> \u2014 The default time to live (TTL), in seconds. This value specifies how long clients cache DNS zone data.<\/li>\n<\/ul>\n

      Edit DNS Zone<\/h2>\n

      The Edit DNS Zone<\/em> interface displays a table of the domain\u2019s DNS entries in the following columns:<\/p>\n

        \n
      • Domain<\/em> \u2014 The domain name.<\/li>\n
      • TTL<\/em> \u2014 The DNS entry\u2019s TTL.<\/li>\n
      • Record Type<\/em> \u2014 The DNS record type.<\/li>\n<\/ul>\n
        \n
        Warning:<\/div>\n
        \n You must<\/strong> set the Class value to IN for each DNS zone.\n <\/div>\n<\/div>\n

        Record Type<\/h3>\n
          \n
        • SOA<\/em> (Start of Authority record) – Contains authoritative information. Authoritative information includes the following information:\n
            \n
          • The authoritative nameserver\u2019s hostname.<\/li>\n
          • The server administrator\u2019s contact email with a period ( .<\/code> ) in place of the @<\/code> character.<\/li>\n
          • The following time-related data:<\/li>\n
          • The serial number, which includes the year, month, date, and time at which you last edited the record.<\/li>\n
          • The time interval during which clients wait before they refresh zone data.<\/li>\n
          • The time interval during which clients wait before they try again after a failed refresh attempt.<\/li>\n
          • The time interval that the record remains valid after clients refresh the zone data.<\/li>\n
          • The minimum TTL.<\/li>\n<\/ul>\n<\/li>\n
          • NS<\/em> (Nameserver record) – Identifies a domain\u2019s authoritative DNS servers.<\/li>\n
          • A<\/em> (IPv4 address record) – Matches a domain name to an IPv4 address.<\/li>\n
          • AAAA<\/em> (IPv6 address record) – Matches a domain name to an IPv6 address.<\/li>\n
          • MX<\/em> (Mail Exchange record) – Identifies the servers that handle mail for a domain. A preference number for each MX record determines in which order other mail servers use a domain\u2019s mail servers.\n
            \n
            Note:<\/div>\n
            \n A lower preference number indicates a higher priority. A preference number of 0 indicates the highest priority.\n <\/div>\n<\/div>\n<\/li>\n
          • CNAME<\/em> (Canonical name record) – Matches a domain name to an alias.<\/li>\n
          • CAA<\/em> (Certificate Authority (CA) Authentication) – Controls which CAs can issue SSL certificates for a domain.\n
            \n
            Important:<\/div>\n
            \n
              \n
            • \n

              We strongly<\/strong> recommend that you add CAA records in this interface or via the following WHM API 1 functions:<\/p>\n

                \n
              • addzonerecord<\/li>\n
              • editzonerecord<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

                The system stores these records in the RFC 3597 format. You can only<\/strong> add CAA records directly to your DNS zone file if you use the BIND nameserver.<\/p>\n

                  \n
                • \n

                  MyDNS does not<\/strong> support CAA records.<\/p>\n<\/li>\n

                • \n

                  If no CAA records exist for a domain, all CAs can issue certificates for that domain. If conflicting CAA records already exist, remove the existing CAA records or add one for the desired CA.<\/p>\n<\/li>\n

                • \n

                  For example, a CAA record for Sectigo would resemble the following example, where example.com<\/code> represents the domain name:<\/p>\n

                  example.com. 86400 IN CAA 0 issue \"sectigoca.com\"\n<\/code><\/pre>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n<\/ul>\n
                  Add entries<\/h3>\n
                  Use the empty text boxes below the Add New Entries Below this Line<\/em> heading to add new entries to the DNS zone.<\/p>\n
                  \n
                  Warning:<\/div>\n
                  \n        You must<\/strong> configure your DNS records correctly to allow visitors to access the domains.\n    <\/div>\n<\/div>\n
                  After you enter the desired information, click Save<\/em>.<\/p>\n
                  Set a separate IP address for the domain and mail server<\/h3>\n
                  If you change the IP address of the domain\u2019s A record, your mail server\u2019s IPv4 address also automatically changes. This occurs because the standard zone template uses a CNAME record to point the mail server to the domain\u2019s A record.<\/p>\n
                  To assign a different IPv4 address to the mail server, perform the following steps:<\/p>\n
                    \n
                  1. \n
                    Change the MX record value to mail.$domain.<\/code>, where $domain.<\/code> represents the domain. For example, change example.com.<\/code> to mail.example.com<\/code>. <\/p>\n
                    \n
                    Important:<\/div>\n
                    \n        You must<\/strong> include the trailing period after mail.example.com<\/code>.\n    <\/div>\n<\/div>\n<\/li>\n
                  2. \n
                    Select CNAME<\/em> from the Record Type<\/em> menu.<\/p>\n<\/li>\n
                  3. \n
                    Click Save<\/em>.<\/p>\n<\/li>\n<\/ol>\n
                    To change the zone template so that all new domains create MX records that assign your mail server a different IP address, use WHM\u2019s Edit Zone Templates<\/em> interface (WHM >> Home  >> DNS Functions >> Edit Zone Templates<\/em>).<\/p>\n
                    Configure email routing<\/h3>\n
                    \n
                    Warning:<\/div>\n
                    \n
                      \n
                    • Misconfigured Email Routing<\/em> settings can disrupt your ability to receive mail. If you are unsure which option to choose, contact your system administrator or hosting provider.<\/li>\n
                    • This interface only displays email routing information for domains that this server hosts. It will not<\/strong> display routing information for domains that other servers host, such as through a DNS Clustering configuration.<\/li>\n<\/ul><\/div>\n<\/div>\n
                      To configure how your server routes mail for the selected domain, perform the following steps:<\/p>\n
                        \n
                      1. \n
                        Select one of the following options under Configure Email<\/em> Routing:<\/p>\n
                          \n
                        • Automatically Detect Configuration<\/em> \u2014 The system uses the following criteria to configure the email routing settings:<\/li>\n
                        • Local Mail Exchanger<\/em> \u2014 The lowest numbered mail exchanger points to an IP address on this server.<\/li>\n
                        • Backup Mail Exchanger<\/em>  \u2014 The lowest numbered mail exchanger points to an IP address not on this server.<\/li>\n
                        • \n
                          Remote Mail Exchanger<\/em> \u2014 No mail exchangers point to an IP address on this server. <\/p>\n
                          \n
                          Note:<\/div>\n
                          \n        If the configured Mail Exchange (MX) records do not resolve, automatic detection will not<\/strong> occur.\n    <\/div>\n<\/div>\n<\/li>\n
                        • \n
                          Local Mail Exchanger<\/em> \u2014 The server always accepts mail for this domain. The system will deliver mail to the local mailbox.<\/p>\n
                          \n
                          Note:<\/div>\n
                          \n        Choose this option if your server uses smart hosts or another gateway service to filter mail.\n    <\/div>\n<\/div>\n<\/li>\n
                        • \n
                          Backup Mail Exchanger<\/em> \u2014 The server functions as a backup mail exchanger. The system will hold mail for this domain until a lower number mail exchanger becomes available.<\/p>\n
                          \n
                          Note:<\/div>\n
                          \n        You must<\/strong> configure the primary MX record to point to the appropriate exchanger.\n    <\/div>\n<\/div>\n<\/li>\n
                        • \n
                          Remote Mail Exchanger<\/em> \u2014 The server will not accept mail for this domain. The system sends all mail for this domain to the lowest numbered mail exchanger.   <\/p>\n
                          \n
                          Note:<\/div>\n
                          \n        You must<\/strong> configure the primary MX record to point to the appropriate exchanger.\n    <\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
                        • \n
                          Click Change<\/em>.<\/p>\n<\/li>\n<\/ol><\/div>\n","protected":false},"excerpt":{"rendered":"
                          Valid for versions 88 through the latest version Version: 82 86 88 Overview This feature allows you to edit the records in a domain\u2019s DNS zone file. Warning: We removed this interface in cPanel & WHM version 96. Use WHM\u2019s DNS Zone Manager interface (WHM >> Home >> DNS Functions >> DNS Zone Manager). For …<\/p>\n","protected":false},"author":1,"featured_media":947,"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\/946"}],"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=946"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/946\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/947"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=946"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=946"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=946"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}