Bug 12120 - Dynamic SOA
Summary: Dynamic SOA
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-06 00:27 UTC by Alex MacCuish
Modified: 2017-06-29 07:13 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex MacCuish 2016-08-06 00:27:13 UTC 
Currently samba4 returns the SOA of an integrated zone with the primary server that created the zone, normally the first provisioned server in a domain. This means that this server is responsible for accepting all ddns updates, as clients direct their updates to the host in the SOA.

Samba4 via either bind-dlz or the internal server should rewrite the SOA with itself as the primary server when queried so that dynamic updates are distributed.
Comment 1 Stefan Metzmacher 2016-08-11 05:18:47 UTC 
We also need to return the SOA record in the authoritative section
when the client asks for a non-existing name in our zone.

That's how clients typically find the server for dynamic dns updates.
Comment 2 Andrew Bartlett 2017-06-29 07:13:08 UTC 
Fixed by c1bf6d24936b5255b9a714f8f252e281b7f82c9f in master for Samba 4.7