Handling resolv.conf on Ubuntu Server 14.04 LTS

Tom H tomh0665 at gmail.com
Sun Jun 15 15:41:29 UTC 2014

On Sat, Jun 14, 2014 at 9:53 AM, Niki Kovacs <info at microlinux.fr> wrote:
> I just don't understand the logic behind this Debian/Ubuntu-specific setup.
> On a bone-headed Slackware server, I just edit a line in /etc/resolv.conf,
> and that's it. No restarting anything.
> On Debian versions prior to Squeeze (Potato, Woody, Sarge, ...) one could
> invoke '/etc/init.d/networking restart' *without* being kicked out from the
> remote session.
> Usually, when there's a *DO NOT EDIT THIS BY HAND* in a configuration file,
> that's a bad omen. I just cringe at the idea of having to reboot a server
> just after editing resolv.conf. But then, no distro's perfect.

"/etc/resolvconf/resolv.conf.d/head" and it's there because if you
edit "/etc/resolv.conf" manually, your changes can be overwritten.

You're moving from slackware to ubuntu and complaining every time that
you find something that's different on ubuntu. Why switch if you are
more familiar with and prefer slackware?!

If you'd like to disable resolvconf:

1) Remove "dns-nameserver[s]" from "/etc/network/interfaces"

2) Change "/etc/resolv.conf" into a file and populate it with

3) Run "echo manual > /etc/init/resolv.override"

More information about the ubuntu-users mailing list