Bug 9742 - DNS updater does not find primary nameserver from SOA RRs.
Summary: DNS updater does not find primary nameserver from SOA RRs.
Status: NEW
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (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: 2013-03-25 17:28 UTC by Kyle Strickland
Modified: 2015-12-06 22:05 UTC (History)
2 users (show)

See Also:

Attachments
Patch to fix DNS update using SOA query (17.04 KB, patch)
2013-03-25 17:28 UTC, Kyle Strickland 		no flags Details
View All 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 Kyle Strickland 2013-03-25 17:28:23 UTC 
Created attachment 8682 [details]
Patch to fix DNS update using SOA query

In our network there are no NS records for our dnsdomain, but there are for the parent domain which handles the subdomain.  By performing an SOA query for either the subdomain or for the desired hostname, you can find the primary nameserver to send the update request to.

Attached is a patch to perform an SOA query, and if that returns no records, to fall back to the current method of checking for NS records.

Also included in the patch is a change to not assume that the domain name is the same as the kerberos realm when creating the security context for updating DNS.  Instead, we pass in the realm to DoDNSUpdate().