Skip to main content

addaddondomain API call fails with "Invalid domain specified: domain name must have a valid TLD label"

Answered
rinkleton

I've got an existing server on WHM 110 where the API call works.  I'm setting up a new server that has WHM 120.  The same API call gives the error: Invalid domain specified: domain name must have a valid TLD label.  However the domain does have a valid TLD label (com). 

A few notes:

  • Addon Domains are enabled in feature manager
  • I have all the tweak settings set to allow remote domains and all of those settings (same between both servers)

It seems like it works when the newdomain is not a subdomain of the primary domain.  Is there some new requirement for this?  I don't like using the subdomains section because it doesn't create a dedicated DNS zone.  And I don't like using alias domains section because it doesn't separate out the VHOSTs in apache which can cause issues with AutoSSL because it has to reissue the cert for every domain in the VHOST every time you park something. 

Comments

11 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  That's interesting - can you let me know the *exact* call (minus any personal info) that you're running both systems so I can test that?

    0
  • rinkleton

    I was originally using the JSON API, but I get the same result on the command line:

    cpapi2 --user=example AddonDomain addaddondomain dir=public_html newdomain=mailer.example.com subdomain=sub-mailer

    the primary domain on this would be example.com

    0
  • cPRex Jurassic Moderator

    Thanks for the additional details.  I confirmed this call doesn't work on version 120 for whatever reason, and the developers weren't sure why that was the case either off the top of their head.  I created case CPANEL-45878 so they can look into that and I'll be sure to post any updates here!

    0
  • rinkleton

    Thanks.  Glad to hear this wasn't intentional.  Looking forward to a fix. 

    0
  • cPRex Jurassic Moderator

    Me too!

    0
  • rinkleton

    Any update on this.  For us it's having the possible side effect of security issues.  Essentially we are stuck on an old version of WHM until this is fixed.  We have new servers which we are paying for and are all ready to go.  We just can't switch over until this is resolved.

    0
  • cPRex Jurassic Moderator

    rinkleton - understood.  I just checked the case and I don't see any updates to share yet, but I'll be sure to post once I hear something!

    0
  • rinkleton

    Thanks, much appreciated.

    0
  • cPRex Jurassic Moderator

    i did bring this up with the team today and they are looking into this now, so hopefully we'll have some action on it soon!

    0
  • rinkleton

    It looks like this is fixed in 124.0.26.  I didn't see a reference to CPANEL-45878 in the change log though. 

    0
  • cPRex Jurassic Moderator

    rinkleton - you're correct, this is fixed now, but it was noted in the changelog a bit odd.  We noted the older case where things broke instead:

    Fixed RE-938: Revert changes from CPANEL-42994.

    so you should see that entry there!

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post