On Wed, 2021-11-03 at 03:33 -0500, Patrick Goetz via samba
wrote:> Hi Daniel -
>
> Thanks for the suggestion!
>
> I'm using Samba 4.15.1 with the built in DNS. I have my own bind9
> server
> (not part of the domain) as the next level up reference DNS.
>
> The A records are set up automatically, but not the PTR records.
>
> I ran `ipconfig /registerdns` as administrator on the W10 domain
> member,
> but nothing changed:
>
> root at samba-dc:/var/lib/samba/bind-dns# host ibs100
> ibs100.ea.linuxcs.com has address 192.168.1.83
>
> root at samba-dc:/var/lib/samba# host 192.168.1.83
> Host 83.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
>
> Oddly, Samba sets up a bind-dns folder (where one would presumably
> find
> zone files), but it's empty:
>
> root at samba-dc:/var/lib/samba/bind-dns# pwd
> /var/lib/samba/bind-dns
> root at samba-dc:/var/lib/samba/bind-dns# ls -a
> . ..
That is meant for the files required for Bind9 if you are using Bind9.
>
> I'm OK with setting this up by hand, but not sure how to go about
> doing
> this. On the other hand, everything seems to be working without the
> PTR
> records, maybe it's fine.
>
> I haven't tried this, but if absolutely necessary I could probably
> set
> up a zone file on my bind9 server for the Samba domain PTR records,
> and
> the Samba DNS server could just refer the request to bind9. This
> works
> perfectly for A and CNAME records, never tried it with PTR (and
> probably
> won't unless it becomes an issue).
No, please don't do that, you are not the first to think of doing it
and it has never worked. If you must point your clients at the Bind9
server, make it forward everything for the AD dns domain to a DC.