(Solved) cPanel Adding AAAA-Record Fails in DNS Zone Manager-Workaround

Free AI web copilot to create summaries, insights and extended knowledge, download it at here

1533

Abstract

rtunately, cPanel does not immediately discard every piece of it’s stack upon first arrival of it’s successive counterpart.<h1 id="e2bf">How to workaround AAAA failure in DNS Zone Manager</h1><a href="https://api.docs.cpanel.net/whm/introduction/">WHM API v1</a> had it’s return to glory this week as it has been revealed that this aged platform holds the key to the continuity of IPv6, the answer to all internet-related issues of the future and possibly introduce world-peace. Currently the only active cPanel software capable of modifying AAAA DNS records is their original API-that they forgot to deactivate and destroy some 6 years ago. Here’s how it works:For those unwilling to restore their previous frameworks to achieve full compatibility WHM API v1 integrations, the cPanel staff has apparently retrofitted their recently debuted Terminal in WHM for compatibility with the years-deprecated API (also, compatible with an actual terminal client), Just enter a command like this:<div id="a79b"><pre>whmapi1 addzonerecord domain=domain.tld name=host.domain.tld class=IN ttl=14400 type=AAAA address=2604:a:b:c::<span class="h

Options

ljs-symbol">d</pre></div>Thanks to the API that, despite having spent several years dormant in the <a href="https://documentation.cpanel.net/display/DD/WHM+API+1+Sections+-+DNS">Legacy Confluence documentation section</a>, was able overcome the odds and restore IPv6 DNS to the world of cPanel.<h1 id="54c7">How to Prevent Future Issues of This Nature</h1>Preventing these types of scenarios in the future is not an impossible task, especially for a team as large (<a href="https://readmedium.com/cpanel-licensing-changes-introduction-of-server-profiles-and-alternatives-for-hosting-providers-657ae504e21a">and as wealthy</a>) as cPanel & co.It begins by reducing the quantity of updates, by increasing the quality of each update.<ol><li>Allocate extra eyes and hours to code review.</li><li>Increase duration and quantity of updates between announcing a feature will be removed in a future update and permanently removing said feature.</li></ol>The scope of a typical cPanel update often includes massive code changes and significant addition/subtraction of multiple major features. These updates are then labeled “Stable” and distributed as such. “Stable” major version updates rarely a full day before the debugging and patching begins.No administrators have the balls to enable automatic updates to Stable branch-how cPanel would have the servers configured-following the default installation procedure.</article></body>

(Solved) cPanel Adding AAAA-Record Fails in DNS Zone Manager-Workaround

After upgrading cPanel/WHM to “Stable” release 96, you might be surprised to see the former DNS Zone Editor has now been completely removed from this shipment. cPanel representatives in the forums mentioned that DNS Zone Manager would eventually replace the Zone Editor, but surprisingly, this change was implemented after just one full release version.

Further, hosts and clients alike that have adopted IPv6 will be met with the following error when attempting to add or modify AAAA records using the new DNS Zone Manager interface:

Error: API failure: (XID 7s3wg9) “host.domain.tld. 14400 IN AAAA ” does not form a valid DNS resource record. (Syntax error, value expected)

This error could have cPanel hosting providers in a panic, considering the incredible volume potential of IPv6 compared with IPv4 and possibility of each entry, modification or removal of AAAA records could possibly become a new case for the support department.

Furthermore, logging all those AAAA tickets (in case future auditing is necessary) could push the limits of the dedicated NAS storage tasked with filing and holding indefinitely ticket meta-data.

Fortunately, cPanel does not immediately discard every piece of it’s stack upon first arrival of it’s successive counterpart.

How to workaround AAAA failure in DNS Zone Manager

WHM API v1 had it’s return to glory this week as it has been revealed that this aged platform holds the key to the continuity of IPv6, the answer to all internet-related issues of the future and possibly introduce world-peace. Currently the only active cPanel software capable of modifying AAAA DNS records is their original API-that they forgot to deactivate and destroy some 6 years ago. Here’s how it works:

For those unwilling to restore their previous frameworks to achieve full compatibility WHM API v1 integrations, the cPanel staff has apparently retrofitted their recently debuted Terminal in WHM for compatibility with the years-deprecated API (also, compatible with an actual terminal client), Just enter a command like this:

whmapi1 addzonerecord domain=domain.tld name=host.domain.tld class=IN ttl=14400 type=AAAA address=2604:a:b:c::d

Thanks to the API that, despite having spent several years dormant in the Legacy Confluence documentation section, was able overcome the odds and restore IPv6 DNS to the world of cPanel.

How to Prevent Future Issues of This Nature

Preventing these types of scenarios in the future is not an impossible task, especially for a team as large (and as wealthy) as cPanel & co.

It begins by reducing the quantity of updates, by increasing the quality of each update.

Allocate extra eyes and hours to code review.

Increase duration and quantity of updates between announcing a feature will be removed in a future update and permanently removing said feature.

The scope of a typical cPanel update often includes massive code changes and significant addition/subtraction of multiple major features. These updates are then labeled “Stable” and distributed as such. “Stable” major version updates rarely a full day before the debugging and patching begins.

No administrators have the balls to enable automatic updates to Stable branch-how cPanel would have the servers configured-following the default installation procedure.