On Fri, 2021-12-10 at 09:46 +0100, Andrea Venturoli via samba
wrote:> Hello.
>
> This is a non-problem, as it doesn't seem to produce any illness;
> it's
> just spamming the logs with warnings and I'm a curious type...
>
> I'm running 4.13.14 as an AD DC in a FreeBSD 12.2 jail.
> Recently I started seeing the following, several times in a day:
>
> >
> I find this strange for several reason:
> _ I've only got one fileserver and two clients here: all have a fixed
> IP
> address, so why samba_dnsupdate is called in the first place?
> _ samba_dnsupdate is running on the DC here, so how can it timeout
> speaking to itself???
> _ obiously name resolution works on that DC ("host
> dc1.ad.xxxx.netfence.it" gives 192.168.128.2 in no time);
> _ I also added "allow dns updates=disabled" to smb.conf, but
nothing
> changed.
It looks fairly obvious, Your DC cannot find its own dns server.
Rowland