Right now is one of those not times so it afforded me the opportunity/need to do some diagnostics.
Turns out issue not with the gateway. Basically:
Code: Select all
dig @192.169.0.1 whatever.lan
Code: Select all
dig whatever.lan
Why?
I find dig's output painful to say the least, so easier is nslookup and:
Code: Select all
nslookup whatever.lan
Code: Select all
Server: 192.168.1.10
Address: 192.168.1.10#53
** server can't find whatever.lan: NXDOMAIN
And now the clues start mounting. Can I force my system to use 192.168.0.1 as DNS? Seems I can't find a way. If I add it to:
Code: Select all
$ cat /etc/resolvconf/resolv.conf.d/base
nameserver 192.168.0.1
Code: Select all
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.10
nameserver 192.168.1.6
nameserver 192.168.0.1
Whence cometh the first two entries and how do I lose them or otherwise achieve resoluton via 192.168.0.1.
Penny dropped and I worked it out! I have vpnc running a VPN! Killed the VPN and then all was good again. Local name resolution works:
Code: Select all
$ nslookup whatever.lan
Server: 192.168.0.1
Address: 192.168.0.1#53
Non-authoritative answer:
Name: whatever.lan
Address: 192.168.0.xx
So the question becomes how can I say to Linux:
Use my gateway FIRST then the VPN DNS!
Why does vpnc insert DNS entries. I want to append them! I want my .lan addresses to resolve with priority!
Would love to understand how to prioritise my local DNS!