DirectAdmin 1.690

[exlhost]

You need to remove dnssec-enable yes; from named.conf, which is no longer supported and can cause problems when starting named.

We do not use outdated software like DirectSlave but simply a BIND or PowerDNS cluster. Also something to consider rather than waiting for a developer from Ukraine.

 

[Richard G]

which is no longer supported and can cause problems when starting named.

It's decreated as from Bind 9.16 but was still working. It was fully removed from 9.18.

Anyway I can confirm it's a 1.690 issue as also with the other server on 1.689 it works flawlessly with creating and deleting.
But on changing records it does not. So might still be something else.

 

[exlhost]

Yes 9.16.* is used in Almalinux 9 and 9.18.* in Almalinux 10.

 

[Richard G]

Yep and on Alma 8 which I'm using on the DS server.

 

[fln]

Regarding the DNS cluster.

The only difference between version 1.690 and 1.689 is that cluster API calls (from main DA server to cluster servers) now adds Content-Type: application/x-www-form-urlencoded header. This affects requests to delete DNS zone and request to add record.

This header correctly describes the request body (URL encoded data). We are adding this header to make cluster calls compatible with servers that automatically decode the request payload based on the content type header.

@Richard G could you please test out a special DA 1.690 build d32f210f685650153589cc0db66d7a1d2cb1dae3. This is the identical build to the normal DA 1.690 but it does not add the new Content-Type header in DNS cluster related API calls. If this build works correctly with directslave tool it would mean addition of the correct Content-Type header causes problems for directslave and explains why it stopped working correctly with DA 1.690.

The addition of correct Content-Type header should have no effect on well-behaving HTTP servers, and it should improve compatibility on servers that actually use this header for content parsing.