Skip to main content

AAAA records API failure - DNS Zone Manager.

MHFraser
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. 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.

Comments

14 comments

Date Votes
  • MHFraser
    adding AAAA records via the WHM api works.
    0
  • cPRex Jurassic Moderator
    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.
    0
  • MHFraser
    Hi I'm using the WHM "DNS Zone manager" interface
    0
  • cPRex Jurassic Moderator
    Thanks for that information. This is a known issue that is resolved in version 98, although our team is looking into a backport for 96 at this time.
    0
  • Moises Perez
    Thanks for that information. This is a known issue that is resolved in version 98, although our team is looking into a backport for 96 at this time.

    Yes, please. Also, are there any plans to make bulk updates available in Manager? It kind of lacks some features, though.
    0
  • cPRex Jurassic Moderator
    Can you let me know what type of bulk updates you're referring to?
    0
  • AzeDK
    Any work-around to fix this for v96 ?
    0
  • cPRex Jurassic Moderator
    At this point I don't have a fix or version 96.
    0
  • AzeDK
    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 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
    0
  • MHFraser
    This is a known issue that is resolved in version 98

    hmmm... 94 broke phpmyadmin for hosts with an ipv6 address. -> you seem to have a blindspot in regards to ipv6
    0
  • cPRex Jurassic Moderator
    There's definitely improvements coming with IPv6 - that's something we're always looking to integrate more with the product.
    0
  • AzeDK
    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?
    0
  • cPRex Jurassic Moderator
    Hey, even we can't catch them all!
    0
  • MHFraser
    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...
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post