Hi John,
While testing the Automatic DNS configuration, I noticed a behaviour that was not quite what I expected.
When a domain already uses Automatic DNS management and the selected publishRecords are changed, newly enabled record families are stored correctly, but no DNS task is scheduled afterwards.
For example, enabling DMARC on an already automatically managed domain updates the domain configuration, but the DNS provider is never reconciled. The new record is therefore not published unless another action happens to trigger DNS provisioning.
I traced this through the current server code and prepared a small fix that schedules one DNS task when new record families are enabled while the domain remains in Automatic mode. Unchanged or merely reordered sets do not create a task, and the existing DKIM, ACME and mode-switch behaviour is preserved.
The patch has been validated with nine focused tests plus compile, rustfmt and Clippy checks.
There is also a second, related point that may be worth clarifying in the UI or documentation.
Automatic DNS currently creates and updates selected records, but removing a type from publishRecords does not remove DNS records that were published previously. I understand why automatic deletion is deliberately conservative here, but the term “Automatic DNS management” can make users expect full desired-state reconciliation.
Something like “Automatic DNS publishing”, or at least a short note next to the Record Types, might describe the current behaviour more accurately:
Unchecking a record type stops future updates. Existing DNS records are not deleted automatically and must be removed manually at the DNS provider.
I will open a separate ticket with the tested patch for the missing publish/reconcile trigger.
Best regards
Stefan