Peter Tuharsky
2019-Feb-08 20:19 UTC
[Samba] Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
like this, Rowland: samba-tool dns add -U administrator 10.20.1.1 interbronz.local asus.interbronz.local A 10.20.4.69 Dňa 7. 2. 2019 o 21:24 Rowland Penny via samba napísal(a):> On Thu, 7 Feb 2019 21:05:12 +0100 > Peter Tuharsky via samba <samba at lists.samba.org> wrote: > >> Well, I have finally installed Samba 4.9 from Van Belle's repo, but >> still I cannot resolve FQDN's. >> > It should work, here is proof: > > rowland at devstation:~/diff$ nslookup dc4 > Server: 192.168.0.6 > Address: 192.168.0.6#53 > > Name: dc4.samdom.example.com > Address: 192.168.0.6 > > rowland at devstation:~/diff$ nslookup dc4.samdom.example.com > Server: 192.168.0.6 > Address: 192.168.0.6#53 > > Name: dc4.samdom.example.com > Address: 192.168.0.6 > > rowland at devstation:~/diff$ nslookup 192.168.0.6 > Server: 192.168.0.6 > Address: 192.168.0.6#53 > > 6.0.168.192.in-addr.arpa name = dc4.samdom.example.com. > > rowland at devstation:~/diff$ ping -c1 dc4 > PING dc4.samdom.example.com (192.168.0.6) 56(84) bytes of data. > 64 bytes from dc4.samdom.example.com (192.168.0.6): icmp_seq=1 ttl=64 time=0.890 ms > > --- dc4.samdom.example.com ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.890/0.890/0.890/0.000 ms > rowland at devstation:~/diff$ ping -c1 dc4.samdom.example.com > PING dc4.samdom.example.com (192.168.0.6) 56(84) bytes of data. > 64 bytes from dc4.samdom.example.com (192.168.0.6): icmp_seq=1 ttl=64 time=0.567 ms > > --- dc4.samdom.example.com ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.567/0.567/0.567/0.000 ms > rowland at devstation:~/diff$ ping -c1 192.168.0.6 > PING 192.168.0.6 (192.168.0.6) 56(84) bytes of data. > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=0.668 ms > > --- 192.168.0.6 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.668/0.668/0.668/0.000 ms > > How are you creating your dns records ? > > Rowland >
Rowland Penny
2019-Feb-08 20:56 UTC
[Samba] Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
On Fri, 8 Feb 2019 21:19:20 +0100 Peter Tuharsky via samba <samba at lists.samba.org> wrote:> like this, Rowland: > > samba-tool dns add -U administrator 10.20.1.1 interbronz.local > asus.interbronz.local A 10.20.4.69 >The syntax is: samba-tool dns add <server> <zone> <name> A <data> From the above: <server> = 10.20.1.1 <zone> = interbronz.local <name> = asus.interbronz.local <data> = 10.20.4.69 Provided '10.20.1.1' is a Samba AD DC, this is okay. Provided 'interbronz.local' is the forward zone, this is okay. Provided '10.20.4.69' is the IP of 'asus.interbronz.local', this is okay. The <name> is wrong, it should just be 'asus' If 'local' is your TLD, then turn off Avahi if it is running, this means anywhere in your Samba AD domain Rowland
Peter Tuharsky
2019-Feb-09 08:12 UTC
[Samba] Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
Thank You Rowland. I did it like You say, killed avahi, added the record without domain suffix, but nothing changed, and the record seems no different compared to other records added with the suffix some time before. My Samba DNS record looks like this (and I see nothing special in there): Name=, Records=3, Children=0 SOA: serial=39, refresh=900, retry=600, expire=86400, minttl=3600, ns=blacktux.interbronz.local., email=hostmaster.interbronz.local. (flags=600000f0, serial=39, ttl=3600) NS: blacktux.interbronz.local. (flags=600000f0, serial=1, ttl=900) A: 10.20.1.1 (flags=600000f0, serial=3, ttl=900) Name=_msdcs, Records=0, Children=0 Name=_sites, Records=0, Children=1 Name=_tcp, Records=0, Children=4 Name=_udp, Records=0, Children=2 Name=asus, Records=1, Children=0 A: 10.20.4.69 (flags=f0, serial=27, ttl=900) Name=blacktux, Records=1, Children=0 A: 10.20.1.1 (flags=f0, serial=2, ttl=900) Name=boss, Records=1, Children=0 A: 10.20.3.78 (flags=f0, serial=39, ttl=900) Name=DomainDnsZones, Records=0, Children=2 Name=ForestDnsZones, Records=0, Children=2 Name=intelhd, Records=1, Children=0 A: 10.20.1.82 (flags=f0, serial=20, ttl=900) Name=w7-virt, Records=1, Children=0 A: 10.10.10.102 (flags=f0, serial=21, ttl=900) Dňa 8. 2. 2019 o 21:56 Rowland Penny via samba napísal(a):> On Fri, 8 Feb 2019 21:19:20 +0100 > Peter Tuharsky via samba <samba at lists.samba.org> wrote: > >> like this, Rowland: >> >> samba-tool dns add -U administrator 10.20.1.1 interbronz.local >> asus.interbronz.local A 10.20.4.69 >> > The syntax is: > samba-tool dns add <server> <zone> <name> A <data> > > From the above: > > <server> = 10.20.1.1 > <zone> = interbronz.local > <name> = asus.interbronz.local > <data> = 10.20.4.69 > > Provided '10.20.1.1' is a Samba AD DC, this is okay. > Provided 'interbronz.local' is the forward zone, this is okay. > Provided '10.20.4.69' is the IP of 'asus.interbronz.local', this is okay. > > The <name> is wrong, it should just be 'asus' > > If 'local' is your TLD, then turn off Avahi if it is running, this > means anywhere in your Samba AD domain > > Rowland >
Maybe Matching Threads
- Phantom DNS records visible with dig, but not samba-tool dns
- Authentication to Secondary Domain Controller initially fails when PDC is offline
- bind-dns Folder Missing for Samba4 Setup in Ubuntu
- which DNS backend ?
- Authentication to Secondary Domain Controller initially fails when PDC is offline