[Samba] Reverse Lookup Zone Not Loaded by DNS Server

[Roy Eastwood]

Hi Louis,

Thanks for your help as always!   See in-line responses below.

> -----Original Message-----
> From: samba <samba-bounces at lists.samba.org> On Behalf Of L.P.H. van Belle via samba
> Sent: 25 May 2021 09:25
> To: samba at lists.samba.org
> Subject: Re: [Samba] Reverse Lookup Zone Not Loaded by DNS Server
> 
> Hai Roy,
> 
> If you change a line like this in systemd : > ExecReload=/usr/sbin/rndc reload
> You MUST be done like this.
> 
> # First empty Variable.
> ExecReload=
> # Set new value.
> ExecReload=/usr/sbin/rndc restart
> 
> Safest way to create the override files is. : systemct edit bind9
> Why like that, that also runs systemctl daemon-reload for you.
> 
> Just to be sure on that.
> 
Yes, that's exactly how I did it.

> I can recall i seen this also with some update last week, on the F5/refresh,
> but, a reboot fixed that for me.
> 
> Hmm, verify the bind0 logs, check if bind9 is running fine.
> The output shown of the reverse zone  looks fine to me.
> 
> journalctl -u bind9
> journalctl -u samba-ad-dc
> 
> You can also do/add this.
> 
> systemctl edit samba-ad-dc
> Part below makes sure samba is started after bind9 has started.
> 
> # /etc/systemd/system/samba-ad-dc.service.d/override.conf
> [Unit]
> After=network.target network-online.target bind9.service
> 

I've added this edit to the samba-ad-dc as suggested.

> 
> So, all i can think of atm, is add these suggestions i gave for the services.
> And reboot the server once more.
> 
> If that didnt work, we need to up the debuglevels in smb.conf.

Rebooted and tried again, but still same error in Windows RSAT DNS Manager.    In case it was particular to that workstation, used another Windows 10 member workstation, but the result is the same.

Have increased the dns log level to 10 in smb.conf, but nothing is jumping out to me, but then again I don't know what I'm looking for!
Here are some snippets from various log files: https://gist.github.com/spindles7/1e812dc83eb61453f149e3d40962d6e2 after restarting the services and opening DNS Manager and pressing F5.

Best regards,
Roy
> 
> 
> Greetz,
> 
> Louis