AAAA records API failure - DNS Zone Manager.

MHFraser

Member
Feb 28, 2019
20
2
3
Australia
cPanel Access Level
Root Administrator
I can no longer add or edit AAAA records in the new DNS zone manager.
its like the actual IP address is missing from the api command
fails with the following error code.

Code:
Error: API failure: (XID 7s3wg9) “xxxx.yyyy.com.au. 14400 IN AAAA ” does not form a valid DNS resource record. (Syntax error, value expected)
other functions appear ok but I haven't tested them all.

can anyone advise of a workaround?
editing the /var/named files directly & restarting named doesn't work.
 
Last edited by a moderator:

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
7,492
1,008
313
cPanel Access Level
Root Administrator
Hey there! Can you let me know the specific API call you were getting an error with so I can test this on my end, as well as how you formatted the command? Just exclude the public information, like the domain name, and I can do some testing.
 

AzeDK

Active Member
Jul 14, 2011
34
17
133
cPanel Access Level
Root Administrator
For other people not familiar with the API, you can use these 3 SSH commands to add, edit, and remove DNS records for AAAA

You can paste them into WHM > Terminal

Code:
whmapi1 addzonerecord domain=example.com name=hostname.example.com class=IN ttl=86400 type=AAAA address=2001:1:42:1::2a

whmapi1 editzonerecord domain=example.com line=24 name=hostname.example.com. class=IN ttl=86400 type=AAAA address=2001:1:42:1::2a

whmapi1 removezonerecord zone=example.com line=4
Notice you need the correct line number for edit and remove, you can see this by opening the DNS Zone file manually in /var/named/example.com.db
 
Last edited:

AzeDK

Active Member
Jul 14, 2011
34
17
133
cPanel Access Level
Root Administrator
Im surprised this bug managed to live all the way into STABLE release without getting caught.

Hows the internal QA testing in those regards with new features?
 

MHFraser

Member
Feb 28, 2019
20
2
3
Australia
cPanel Access Level
Root Administrator
There's definitely improvements coming with IPv6
well thats good to hear.
imagine if the dns manager couldn't add or edit A records - it would be a classified a disaster and a fix pushed out overnight?

I know in some circles ipv6 is considered non-prod still but ipv4 exhaustion is pretty much upon us in APNIC territory.
additional ipv4 addresses need justification now
Consequently I try and do as much as possible with ipv6 as I through my server hosting I can get a ipv6 /48 for nothing...
 
  • Like
Reactions: AzeDK