Luca Olivetti
2019-Sep-09 10:59 UTC
[Samba] samba internal dns doesn't return NXDOMAIN (bug 12464)
Hello, I'm using samba 4 with the internal dns. I'm following the instructions here https://support.mozilla.org/en-US/kb/configuring-networks-disable-dns-over-https to configure my dns server to return NXDOMAIN for use-application-dns.net. If I query the server directly it returns NXDOMAIN, but if I query samba I get an empty answer instead (192.168.90.29 is configured as dns forwarder for both DCs): luca at seis:~$ host use-application-dns.net 192.168.90.29 Using domain server: Name: 192.168.90.29 Address: 192.168.90.29#53 Aliases: Host use-application-dns.net not found: 3(NXDOMAIN) luca at seis:~$ host use-application-dns.net dc1 Using domain server: Name: dc1 Address: 192.168.90.2#53 Aliases: luca at seis:~$ host use-application-dns.net dc2 Using domain server: Name: dc2 Address: 192.168.90.5#53 Aliases: dc1 is running on debian jessie/samba 4.2.14 (I know, I have to upgrade it, but I cannot right now) dc2 is running on debian stretch/samba 4.5.16 I see there's a bug for that https://bugzilla.samba.org/show_bug.cgi?id=12464 but there's no comment after 2016. Has it been solved in some later version? Bye -- Luca Olivetti Wetron Automation Technology http://www.wetron.es/ Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007
Possibly Parallel Threads
- dns replication error due to deleted records
- dns replication error due to deleted records
- Cannot access the (old) samba server on my router from Linux
- dns replication error due to deleted records
- The sad state of samba 4 adaption for home/small business routers.