Conversation
Up until now, the SOA format returned by the internal DNS server
used the zone's name for the primary dns server field, and either
the first dns.nameservers entry or hostmaster.{.zone} for the contact
address.
Instead, use the first entry in dns.nameservers for the master dns
server if set, and adjust the contact address accordingly.
Old SOA entry (no dns.nameserver set):
incus.example.com. 3600 IN SOA incus.example.com. hostmaster.incus.example.com. 1769025229 120 60 86400 30
Old SOA entry (with dns.nameserver set):
incus.example.com. 3600 IN SOA incus.example.com. ns1.example.com. 1769025229 120 60 86400 30
New SOA entry (no dns.nameserver set):
incus.example.com. 3600 IN SOA incus.example.com. hostmaster.incus.example.com. 1769025229 120 60 86400 30
New SOA entry (with dns.nameserver set):
incus.example.com. 3600 IN SOA ns1.example.com. hostmaster.ns1.example.com. 1769025229 120 60 86400 30
Signed-off-by: Dan McGregor <[email protected]>
Adds a new `dns.contact` configuration option to zones. Signed-off-by: Dan McGregor <[email protected]>
Signed-off-by: Stéphane Graber <[email protected]>
Signed-off-by: Stéphane Graber <[email protected]>
github-actions
bot
added
Documentation
stgraber
approved these changes
Jan 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the DNS zone template to use the first entry in dns.nameservers as the primary server, and allow specifying the zone's contact address.
Previously if dns.nameservers was unset the SOA record used the zone name in the MNAME field, and hostmaster.zone_name in the RNAME field. That's as correct as can be considering we have no way to know the primary server's name. However, if dns.nameservers was set, the MNAME field still contained the zone name, and the RNAME field was the name of the primary server. That can cause confusion if downstream servers need to know the primary server's name.
The new behaviour uses the first entry in dns.nameservers as MNAME, and the new dns.contact value as RNAME if set.