[wplug] The history of DNS.... Resolvers
Drew from Zhrodague
drewzhrodague at zhrodague.net
Tue Aug 15 10:25:26 EDT 2017
I haven't worked with dnsmasq much, but name resolution is directed by
/etc/nsswitch.conf, which will list which order the various
name-resolution bits should be used. Mine at home says this:
hosts: db files nisplus nis dns
'files' is the entry that will use /etc/hosts, and I believe 'dns' will
use /etc/resolv.conf.
Nice to see some traffic on the list!
> I was recently having problems with my DNS resolving and cn open a web page
> but I could ping any ip address. This happened after removing the cludgy
> multiboot software. It left behind "tailings" I'd like to call them. It
> took me a little time to figure out that qemu had left behind some virtual
> interfaces. After I removed them, I regained some connectivity. However,
> my host name was not resolving. Apparently, systemd could not resolve any
> dns servers and was not seeing my modem's hostname.home. So when time
> allowed, Okay, it was pretty obvious that my rig's DNS resolver was not
> configured correctly Duh. So I began a sojourn, looking to resolvers.
> through my travails, I installed dnsmasq and disabled sustemd-network.
> Added Open DNS servers to my fios modem, /var/run/NetworkManager/resolv.conf,
> the requisite resolv.conf for dnsmasq and restarted. Wahla!. That brings
> me to my question, How many resolvers are there for linux and how do they
> play/not play together. I noticed from posts online that users depending
> on their needs us network-manager or dnsmasq or dns-sd (old an apple
> program?) I'm curious, anybody? I'm currently running Linux Mint 18.1 on
> my desktop.
--
Drew from Zhrodague
More information about the wplug
mailing list