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

3.5.1 released.

→ FIXED - DirectAdmin 1.69 compatibility for /CMD_API_DNS_ADMIN:

· Proper handling of action=delete when parameters are sent in POST body (form-urlencoded), not only in query string.
· Backward compatible with older DirectAdmin versions that send action/select0 in the URL.
· Added robust request parsing fallback for cases where DA omits Content-Type.

→ Improved rawsave handling:

· dns_write_post.sh added (see /scripts) · Zonefile content is taken directly from request body and passed to dns_write_post.sh.
· Prevents losing POST body after form parsing.
· Delete now supports multiple domains in a single request (select0..selectN).
· Domain deletion is idempotent in DNS-less/dev setups (no false failures when zone artifacts are missing).

Please update to 3.5.1

Also you can support my work and future development of DS
 
roman_m said:
→ FIXED - DirectAdmin 1.69 compatibility for /CMD_API_DNS_ADMIN:
Click to expand...
@roman_m Unfortunately it is not fixed.

I just tested with Directadmin 1.690 and could create a user with a testdomain.
Then I tested adding A and TXT record, which went fine.
Tested removing A record and change of TXT record. Also went fine.

As a last test I tested the removal of the user including the domain. There it went wrong.
Directadmin removed the user and domain from the server. But on the Directslave server, the domain was -not- deleted from the directslave.inc and also the domain .db file was not deleted.

Same as before, only error notice in the Directadmin error.log:
Code: 
Cluster dsvps.server.nl: Error deleting remote dns zone (testdomein.nl): No action taken
Nothing to be seen in directslave logs.

Edit: Sorry my bad I was too enthousiastic. I overwritten everything and forgotten that I renamed the longer binary name to just directslave, so the older version was started again.

Works perfectly now!
 
Last edited:
Richard G said:
@roman_m Unfortunately it is not fixed.

I just tested with Directadmin 1.690 and could create a user with a testdomain.
Then I tested adding A and TXT record, which went fine.
Tested removing A record and change of TXT record. Also went fine.

As a last test I tested the removal of the user including the domain. There it went wrong.
Directadmin removed the user and domain from the server. But on the Directslave server, the domain was -not- deleted from the directslave.inc and also the domain .db file was not deleted.

Same as before, only error notice in the Directadmin error.log:
Code: 
Cluster dsvps.server.nl: Error deleting remote dns zone (testdomein.nl): No action taken
Nothing to be seen in directslave logs.
Click to expand...
Enable debug in DS config, then restart directslave service and do some pipeline tests. Then email me error.log content.
 
Sorry, I will report back soon, seems 3.4.3 was still running.

Edit: Confirmed, 3.5.1. is working as a sunshine, perfectly!!
 
Last edited:
Richard G said:
Yes. At least for domains with ipv6. Most likely making connections on ipv6 too, not tested yet.
Click to expand...
If both servers are IPv6 compatible and have a dedicated IPv6 setup, then yes you can connect via IPv6. Simply use that IP address in the multiserver connection, provided DA have fixed it, which they hadn't up to version 1.691 (It broke when they updated something in 1.686)

You'd have to edit the /usr/local/directadmin/data/admin/cluster.conf file to add one at the moment.
 
You must log in or register to reply here.
Back
Top