Making resolv.conf changes permanant

[Karl Auer]

On Thu, 2015-04-30 at 11:39 -0500, Chris wrote:
> When I'm finished I run sudo resolvconf -u and /etc/resolv.conf reverts

Look in /etc/resolvconf/resolv.conf.d for two ways to control what ends
up in resolv.conf - the contents of "base" and "head" will be inserted
verbatim.

The business with "nameserver 127.0.1.1" is caused by NetworkManager
running dnsmasq. If you are supplying your own nameserver
infrastructure, you can simply uninstall or disable dnsmasq, and this
behavior will go away.

For example, edit this file:

   /etc/NetworkManager/NetworkManager.conf

... and comment out the line that says "dns=dnsmasq". You will need to
restart NetworkManager; you may need to reboot or manually kill any
running instance of dnsmasq (not sure about this, it's been a while).

Theoretically it should be possible to change how NetworkManager runs
dnsmasq - for example by telling it not to use resolv.conf. I've never
bothered, I just uninstall it.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: 3C41 82BE A9E7 99A1 B931 5AE7 7638 0147 2C3C 2AC4
Old fingerprint: EC67 61E2 C2F6 EB55 884B E129 072B 0AF0 72AA 9882