DirectSlave - solution to add and remove zones on slave without DirectAdmin

[Richard G]

Check the directslave error log.

I found recently after some OS or bind update that the /etc/named directory restored original permissions and owner from root.
So now I changed it and now use a self created /etc/namedb directory with correct owner and permission and things work again.

However, in your case it might be something else, so it's always best to check the logs at the directslave server to see why things went wrong.

 

[reonhoub2]

Of course. I also checked the log data on the Directslave server. There is no entry for deleting the domain. New zones can be added without any problems.

directadmin error log:

/var/log/directadmin/error.log:2025:12:15-19:05:01: Cluster ns1.mydomain.de: Error deleting remote dns zone (gwefibgw.de): No action taken
/var/log/directadmin/error.log:2025:12:15-19:05:02: Cluster ns2.mydomain.de: Error deleting remote dns zone (gwefibgw.de): No action taken

directslave access log:

2025/12/15 19:04:02 [xxx.xxx.xxx.xxx] "GET /CMD_API_DNS_ADMIN?action=exists&domain=gwefibgw.de HTTP/1.0"
2025/12/15 19:04:06 [xxx.xxx.xxx.xxx] "GET /CMD_API_DNS_ADMIN?action=exists&domain=gwefibgw.de HTTP/1.0"
2025/12/15 19:04:06 [xxx.xxx.xxx.xxx] "POST/CMD_API_DNS_ADMIN?action=rawsave&domain=gwefibgw.de&username=admin&hostname=mydomain.de HTTP/1.0"
2025/12/15 19:04:06 [xxx.xxx.xxx.xxx] "POST/CMD_API_DNS_ADMIN?action=rawsave&domain=gwefibgw.de&username=admin&hostname=mydomain.de HTTP/1.0"
2025/12/15 19:04:46 [xxx.xxx.xxx.xxx] "GET /CMD_API_DNS_ADMIN?action=exists&domain=gwefibgw.de HTTP/1.0"
2025/12/15 19:04:46 [xxx.xxx.xxx.xxx] "GET /CMD_API_DNS_ADMIN?action=exists&domain=gwefibgw.de HTTP/1.0"
2025/12/15 19:04:46 [xxx.xxx.xxx.xxx] "POST/CMD_API_DNS_ADMIN?action=rawsave&domain=gwefibgw.de&named_reload=yes&username=admin&hostname=mydomain.de HTTP/1.0"
2025/12/15 19:04:46 [xxx.xxx.xxx.xxx] "POST/CMD_API_DNS_ADMIN?action=rawsave&domain=gwefibgw.de&named_reload=yes&username=admin&hostname=mydomain.de HTTP/1.0"
2025/12/15 19:05:03 [xxx.xxx.xxx.xxx] "POST /CMD_API_DNS_ADMIN HTTP/1.0"

directslave action log:

2025/12/15 19:04:02 Authorization passed for myserver from xxx.xxx.xxx.xxx
2025/12/15 19:04:02 Checking gwefibgw.de from xxx.xxx.xxx.xxx
2025/12/15 19:04:02 Domain gwefibgw.de not exists
2025/12/15 19:04:06 Authorization passed for myserver from xxx.xxx.xxx.xxx
2025/12/15 19:04:06 Checking gwefibgw.de from xxx.xxx.xxx.xxx
2025/12/15 19:04:06 Domain gwefibgw.de not exists
2025/12/15 19:04:06 Authorization passed for myserver from xxx.xxx.xxx.xxx
2025/12/15 19:04:06 Domain gwefibgw.de added with primary xxx.xxx.xxx.xxx
2025/12/15 19:04:17 RNDC queue triggered with 1 events
2025/12/15 19:04:18 RNDC output: server reload successful
2025/12/15 19:04:46 Authorization passed for myserver from xxx.xxx.xxx.xxx
2025/12/15 19:04:46 Checking gwefibgw.de from xxx.xxx.xxx.xxx
2025/12/15 19:04:46 Domain gwefibgw.de exists on primary xxx.xxx.xxx.xxx
2025/12/15 19:04:46 Authorization passed for myserver from xxx.xxx.xxx.xxx
2025/12/15 19:04:46 Checking gwefibgw.de from xxx.xxx.xxx.xxx
2025/12/15 19:04:46 Domain gwefibgw.de exists on primary xxx.xxx.xxx.xxx
2025/12/15 19:04:46 Authorization passed for myserver from xxx.xxx.xxx.xxx
2025/12/15 19:04:46 Reloaded gwefibgw.de from master xxx.xxx.xxx.xxx
2025/12/15 19:04:48 RNDC queue triggered with 1 events
2025/12/15 19:04:49 RNDC output: server reload successful
2025/12/15 19:05:03 Authorization passed for myserver from xxx.xxx.xxx.xxx
2025/12/15 19:16:43 Authorization passed for myserver from xxx.xxx.xxx.xxx

No relevant entries in directslave error log.

I therefore assumed that it was a general problem. Does deleting still work for you with DA 1.690 and Directslave 3.4.3?

 

[Richard G]

Does deleting still work for you with DA 1.690 and Directslave 3.4.3?

Even worse.

I just tested for you and I got my testdomain in the directslave.inc file but the testdomain.nl.db file wasn't even created.
Also no error in the error log.

And I also found testdomains in the directslave.inc file which were created a couple of days ago when I changed the connection to SSL.

Looks indeed something in Directadmin 1.690 or 1.689 maybe changed which has influence on Directslave. Maybe @romans knows?

However it's still odd that DS does create the line in Directslave but then does not create the .db file. So I'm not sure if this is something of an OS update or DA update.
I'm running DS on Almalinux 8.10.

Edit: also in my case only an error notice in the directadmin error.log which oddly enough is in an already rotaded logfile:

2025:12:16-02:07:47: Cluster directslave.server.nl: Error deleting remote dns zone (eventesten.com): No action taken

Odd thing, this is the file:
error.log-20251214

Now logrotate it probably at 02.00 hours, but in the normal error.log file I see this:

2025:12:16-02:00:30: Socket::curl_request: curl returned code 6: curl: (6) Could not resolve host: (null)
2025:12:16-02:00:36: Socket::curl_request: curl returned code 6: curl: (6) Could not resolve host: (null)
2025:12:16-02:00:43: Socket::curl_request: curl returned code 6: curl: (6) Could not resolve host: (null)
2025:12:16-02:01:15: clean_dangerious_env_vars:Spam::saveSettings: cleared dangerous variable: SAFE_CODE=
2025:12:16-02:01:16: getHomeDir: username is empty!:

No clue what it means, but just strange that what happens at 02.07 hours is logged to an older already rotated logfile.