dc01 looks to be using 10.0.0.1 for its DNS resolver
On Sat., Sep. 10, 2022, 12:05 p.m. Rob Campbell via samba, <
samba at lists.samba.org> wrote:
> From my DC (DC01):
> [Sat Sep 10 14:58:30] [root at DC01~$] host dc01
> dc01 has address 10.0.0.10
> [Sat Sep 10 14:58:33] [root at DC01~$] host dc01.home.rob-campbell.lan
> Host dc01.home.rob-campbell.lan not found: 3(NXDOMAIN)
> [Sat Sep 10 14:58:38] [root at DC01~$] host 10.0.0.10
> 10.0.0.10.in-addr.arpa domain name pointer DC01.
> [Sat Sep 10 14:58:45] [root at DC01~$] nslookup dc01
> Server: 10.0.0.1
> Address: 10.0.0.1#53
>
> Name: dc01
> Address: 10.0.0.10
>
> [Sat Sep 10 14:59:06] [root at DC01~$] nslookup dc01.home.rob-campbell.lan
> Server: 10.0.0.1
> Address: 10.0.0.1#53
>
> ** server can't find dc01.home.rob-campbell.lan: NXDOMAIN
>
> [Sat Sep 10 14:59:18] [root at DC01~$] host dc02
> Host dc02 not found: 3(NXDOMAIN)
> [Sat Sep 10 15:00:58] [root at DC01~$] host dc02.home.rob-campbell.lan
> Host dc02.home.rob-campbell.lan not found: 3(NXDOMAIN)
> [Sat Sep 10 15:01:06] [root at DC01~$] host 10.0.0.9
> Host 9.0.0.10.in-addr.arpa. not found: 3(NXDOMAIN)
> [Sat Sep 10 15:01:12] [root at DC01~$] nslookup dc02
> Server: 10.0.0.1
> Address: 10.0.0.1#53
>
> ** server can't find dc02: NXDOMAIN
>
> [Sat Sep 10 15:01:21] [root at DC01~$] nslookup dc02.home.rob-campbell.lan
> Server: 10.0.0.1
> Address: 10.0.0.1#53
>
> ** server can't find dc02.home.rob-campbell.lan: NXDOMAIN
>
> From my workstation DC02:
>
> [Sat Sep 10 14:59:47] [root at dc02~$] host dc01
> dc01.HOME.ROB-CAMPBELL.LAN has address 10.0.0.10
> dc01.HOME.ROB-CAMPBELL.LAN has IPv6 address 2600:4040:4666:f900::1bac
> [Sat Sep 10 14:59:58] [root at dc02~$] host dc01.home.rob-campbell.lan
> dc01.home.rob-campbell.lan has address 10.0.0.10
> dc01.home.rob-campbell.lan has IPv6 address 2600:4040:4666:f900::1bac
> [Sat Sep 10 15:00:10] [root at dc02~$] host 10.0.0.10
> Host 10.0.0.10.in-addr.arpa. not found: 3(NXDOMAIN)
> [Sat Sep 10 15:00:16] [root at dc02~$] nslookup dc01
> Server: 10.0.0.10
> Address: 10.0.0.10#53
>
> Name: dc01.HOME.ROB-CAMPBELL.LAN
> Address: 10.0.0.10
> Name: dc01.HOME.ROB-CAMPBELL.LAN
> Address: 2600:4040:4666:f900::1bac
>
> [Sat Sep 10 15:00:25] [root at dc02~$] nslookup dc01.home.rob-campbell.lan
> Server: 10.0.0.10
> Address: 10.0.0.10#53
>
> Name: dc01.home.rob-campbell.lan
> Address: 10.0.0.10
> Name: dc01.home.rob-campbell.lan
> Address: 2600:4040:4666:f900::1bac
>
> [Sat Sep 10 15:00:35] [root at dc02~$] host dc02
> dc02.HOME.ROB-CAMPBELL.LAN has address 10.0.0.9
> [Sat Sep 10 15:01:46] [root at dc02~$] host dc02.rob-campbell.lan
> [Sat Sep 10 15:01:53] [root at dc02~$] host 10.0.0.9
> Host 9.0.0.10.in-addr.arpa. not found: 3(NXDOMAIN)
> [Sat Sep 10 15:02:00] [root at dc02~$] nslookup dc02
> Server: 10.0.0.10
> Address: 10.0.0.10#53
>
> Name: dc02.HOME.ROB-CAMPBELL.LAN
> Address: 10.0.0.9
>
> [Sat Sep 10 15:02:08] [root at dc02~$] nslookup dc02.home.rob-campbell.lan
> Server: 10.0.0.10
> Address: 10.0.0.10#53
>
> Name: dc02.home.rob-campbell.lan
> Address: 10.0.0.9
>
> I'm using samba as my DNS... Or at least I thought I was. LOL.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> In all things, Be Intentional.
>
>
> On Sat, Sep 10, 2022 at 2:37 PM Thomas Cameron via samba <
> samba at lists.samba.org> wrote:
>
> > On 9/9/22 18:20, Rob Campbell via samba wrote:
> > > nslookup 10.0.0.10
> > > 10.0.0.10.in-addr.arpa name = DC01.
> >
> > This is wrong, as I understand it. You want reverse ip addresses to
come
> > back with the FQDN, I think.
> >
> > Here's how my network responds with ip address lookups:
> >
> > [thomas.cameron at case Desktop]$ host case
> > case.tc.camerontech.com has address 172.31.100.4
> > [thomas.cameron at case Desktop]$ host case.tc.camerontech.com
> > case.tc.camerontech.com has address 172.31.100.4
> > [thomas.cameron at case Desktop]$ host 172.31.100.4
> > 4.100.31.172.in-addr.arpa domain name pointer case.tc.camerontech.com.
> > [thomas.cameron at case Desktop]$ nslookup case
> > Server: 127.0.0.53
> > Address: 127.0.0.53#53
> >
> > Non-authoritative answer:
> > Name: case.tc.camerontech.com
> > Address: 172.31.100.4
> >
> > [thomas.cameron at case Desktop]$ nslookup case.tc.camerontech.com
> > Server: 127.0.0.53
> > Address: 127.0.0.53#53
> >
> > Non-authoritative answer:
> > Name: case.tc.camerontech.com
> > Address: 172.31.100.4
> >
> > [thomas.cameron at case Desktop]$ nslookup 172.31.100.4
> > 4.100.31.172.in-addr.arpa name = case.tc.camerontech.com.
> >
> > Authoritative answers can be found from:
> >
> > [thomas.cameron at case Desktop]$
> >
> > I won't swear to it, but I am *pretty* sure that DNS is supposed
to
> > return the FQDN.
> >
> > For reference, I run my own BIND server. I don't rely on Samba to
do
> > DNS, I have a separate DNS server in my environment. My zone files
look
> > like this (this is two lines, in case it gets trimmed):
> >
> > [root at wintermute ~]# grep case /var/named/*
> > /var/named/100.31.172.in-addr.arpa:4 PTR
case.tc.camerontech.com.
> > /var/named/tc.camerontech.com:case IN 1H A
> > 172.31.100.4
> >
> > Hope this helps!
> > Thomas
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions: https://lists.samba.org/mailman/options/samba
> >
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>