On Wed, 17 Jan 2024 09:58:06 +0100
Luis Peromarta via samba <samba at lists.samba.org> wrote:
> Tobias,
>
> Appreciate your insight, it is just nice to have, but I hate when
> things don?t go as expected. I?m going to fight this a little, just
> to see If I am doing anything wrong - but not that it?s critical to me
>
> Thanks,
> On Jan 17, 2024 at 09:48 +0100, Pluess, Tobias <tpluess at ieee.org>,
> wrote:
> >
> > Hi Luis
> >
> > I noticed exactly the same behaviour.
> > I wonder if the PTR record is really required for proper function,
> > or if it is just "nice to have". Because, so far, I could
not
> > observe any adverse effects due to nonexistent PTR records. On the
> > other hand, I recently switched the DNS server. I installed a
> > separate DHCP server using dnsmasq, that also does DHCP and
> > automatically creates the DNS records for the hosts on-the-fly as
> > they register with DHCP. And this also creates the PTR records
> > reliably. The Active Directory/Samba DNS is not used anymore, just
> > for the _ldap and _kerberos SRV records. Everything else is served
> > from the external DNS. With this, I can have all sorts of records
> > reliably.
Two observations:
'Tobias' seems to have contacted 'Luis' directly, not a good
idea, it
breaks the thread flow.
It also isn't a good idea to use dnsmasq as the dns server for Samba AD
unless it forwards everything to a Samba AD dns server and to do this
will require two dns domains e.g. example.com for dnsmasq and
ad.example.com for the Samba dns domain.
Coming back to the original problem, Windows clients do not, by
default, update their PTR records, they have to be told to do so.
Rowland