Skip to main content

WHM api 1 addzonerecord do not work when domain is not on same server

Comments

5 comments

  • cPanelMichael
    Hello :) To clarify, do you mean the domain name is added to the DNS cluster and the zone is in the /var/named directory, but there's no cPanel account for it on the local server? Thank you.
    0
  • kjg
    Hello :) To clarify, do you mean the domain name is added to the DNS cluster and the zone is in the /var/named directory, but there's no cPanel account for it on the local server? Thank you.

    Exactly. The domain name is in the nameserver (so it is in /var/named/thedomain.db) and can be edited via WHM Edit Zone functionality or via WHM API 0 but not via WHM API 1. There is no cPanel account for the domain on the local (nameserver) server.
    0
  • kjg
    Just to update, the same problem exists also for getzonerecord and editzonerecord. They all give the same error when the domain is not an account on the server where the nameserver is located:
    API failure: This system does not have a domain named "existingdomain.com"
    Can't find any way around this and really want to skip all API 0 calls when I rewrite a lot of stuff. Any suggestion would be very much appreciated // kjg
    0
  • kjg
    Hi Michael Can you confirm this? Is it a bug that I should report, or is it just me ... Thank you.
    0
  • cPanelMichael
    Upon further investigation, this behavior is by design. Allowing this behavior is considered a security flaw because it would permit unauthorized zone modifications. CPANEL-2323 is open to determine the best method of restoring this behavior. Thank you.
    0

Please sign in to leave a comment.