I have a slackware64 14.1 Linux host which acts as Samba4 DC/AD and is the domain DNS. I am using the Linux bind v. 9.9.5, not the bind built into Samba4. The Windows workstation DHCP clients work just fine.
I am having problems with a troublesome Slackware 14.1 client. I believe I have found the culprit, but first the problems:
1. `hostname -f` just returns the hostname, not the FDQN.
2. `host hplaptop` (a domain workstation) returns:
$ host hplaptop
Host hplaptop not found: 3(NXDOMAIN)
Config files are:
# Generated by dhcpcd from wlan0, eth1
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
The culprit appears to be the 1st nameserver line in /etc/resolv.conf "nameserver 192.168.1.1". When I comment out this line in resolv.conf my problems go away.
The domain I care about is 192.168.0.0/24 and the DC/AD DNS is 192.168.0.2, as shown. However, the viao host also has a wireless card and its DHCP assigned IP is 192.168.1.154 (assigned from some wireless device in the building not associated with the hprs.local domain).
Therefore I conclude that the problem is that network resolution requests are going the to wireless nameserver which doesn't find the requested host(s). Even when I leave 192.168.1.1 uncommented but move it *after* 192.168.0.2 things still work.
So, long description but here are the questions:
I thought if DNS lookup failed with one nameserver it would try the next. Why doesn't it try 192.168.0.2 when 192.168.1.1 returns "Host hplaptop not found: 3(NXDOMAIN)"?
Can I do anything to a) get it to look at all name servers? If not b) get the 192.168.1.1 nameserver listed 2nd? If not c) not put 192.168.1.1 into /etc/resolv.conf at all (that file is auto-generated by dhcpd)?