[Samba] Missing new NS record.

Zane Zakraisek doublezane at gmail.com
Fri Aug 19 13:25:15 UTC 2016

Yes I shut down the original DC, and noticed most of the AD relient
services were hanging, and I think the culprit was DNS on the new DC.
Would you guys recommend waiting for 4.5, or switching to the BIND backend?
The only reason that I chose the internal DNS server in the first place was
that I thought Kai said the BIND side wasn't getting as much love these

On Thu, Aug 18, 2016 at 6:38 PM, Garming Sam <garming at catalyst.net.nz>

> On 19/08/16 04:17, Rowland Penny via samba wrote:
> > I couldn't find anything that explicitly says that each DC should have
> > its own SOA in AD. What I could find was that each AD-integrated zone on
> > a DC is expected to have a SOA record containing the DCs ipaddress.
> > this indicates that the DC hosts a writable copy of the zone. The SOA
> > should also contain an NS record for the DC. Whilst I do not know how
> > windows does this, the only way I have found to do all this, is to
> > add the DCs A & NS records to the SOA record, only problem is, it
> > only seems (for me) to work with Bind9 as the DNS server.
> >
> I think Windows just clobbers the SOA on the way out. I don't think I've
> seen any documentation describe the behaviour in detail either.
> As for the missing record, Samba 4.5 should fix the immediate problem of
> the actual missing NS record, but currently only using BIND9 DLZ
> actually ensures it is used as a useful nameserver.
> Cheers,
> Garming

More information about the samba mailing list