Pro tip: Take back control of resolv.conf

If you're tired to play hide-and-seek with your configuration files, just use Slackware. A distribution that doesn't follow every stupid new trend.

Agreed. In fact, I'm pretty sure the default configuration of dnsmasq with Slackware doesn't overwrite the resolv.conf file, but instead uses it to determine what nameservers to pass to the machines requesting ip addresses.

Now, if you use wicked or network manager, that's another matter.

Learning to use dnsmasq is a better solution. It was putting the localhost address in resolve.conf so dnsmasq would act as a dns cache. Just put the wanted DNS server addresses in dnsmasq.conf, or uninstall it completely if you aren't going to make use of it. It doesn't even make sense to blame dnsmasq when most distributions have a network manager that automatically put DNS numbers for connections served via DHCP in resolv.conf.

Jack is a rube.

Here's everything you want to know about Dnsmasq configuration under Slackware.

https://kikinovak.wordpress.com/2015/04/24/mettre-en-place-u...

> Here's everything you want to know about Dnsmasq configuration under Slackware.

I think I had to change all of five lines in the configuration file to get things working, The only one that took any effort was telling dnsmasq that the machine it was running on wasn't the gateway. The rest were obvious given the configuration comments in the file.