On Mon, 22 Jul 2024 15:43:26 +0100
miguel medalha via samba <samba at lists.samba.org> wrote:
> I just joined two new DCs to a domain. I created new PTR records for
> them like this:
>
> samba-tool dns add dc1.mydomain.com 10.168.192.in-addr.arpa 8 PTR
> newdc.mydomain.com
> Record added successfully
>
> samba-tool dns query adiafa 10.168.192.in-addr.arpa @ PTR
> Name=8, Records=1, Children=0
> PTR: newdc.mydomain.com (flags=f0, serial=162, ttl=900)
>
> nslookup 192.168.10.8
> ** server can't find 8.10.168.192.in-addr.arpa: NXDOMAIN
>
> The same happens with the other DC and with a new Samba domain member.
> However, with other servers whose PTR records were added from Windows
> RSAT:
>
> nslookup 192.168.10.1
> 1.10.168.192.in-addr.arpa name = someserver.mydomain.com
>
> Does anyone know what's going on?
>
I have no idea, mainly because it just works for myself :-(
adminuser at tmpdc1:~ $ sudo samba-tool dns add tmpdc1.samdom.example.com
samdom.example.com testdc A 192.168.1.8
Password for [administrator at SAMDOM.EXAMPLE.COM]:
Record added successfully
adminuser at tmpdc1:~ $ nslookup testdc
Server: 192.168.1.2
Address: 192.168.1.2#53
Name: testdc.samdom.example.com
Address: 192.168.1.8
adminuser at tmpdc1:~ $ sudo samba-tool dns add tmpdc1.samdom.example.com
1.168.192.in-addr.arpa 8 PTR testdc.samdom.example.com
Password for [administrator at SAMDOM.EXAMPLE.COM]:
Record added successfully
adminuser at tmpdc1:~ $ nslookup 192.168.1.8
8.1.168.192.in-addr.arpa name = testdc.samdom.example.com.
I know this not much help, but I suggest you double check everything.
Rowland