Why is /etc/resolv.conf on tmpfs?
matt.joyce at gmail.com
Sun Aug 10 03:51:20 CEST 2008
Esben Stien wrote:
> Dirk Bergstrom <openmoko at otisbean.com> writes:
>> I thought that resolv.conf was getting wiped out at every boot
> It is and it should be. Use resolveconf.
> /etc/resolvconf/resolv.conf.d/head is the header file for the dynamic
> generation. Leave this alone.
> /etc/resolvconf/resolv.conf.d/base is the "meat" of the file, or the
> middle. Define your nameservers here using this syntax: "nameserver
> xxx.xxx.xxx.xxx" where xxx.xxx.xxx.xxx is the ip of your nameserver.
> /etc/resolvconf/resolv.conf.d/tail is the ending of this file. Leave
> this one alone too.
> /etc/resolvconf/resolv.conf.d/original is the original configuration
> of the file. These isn't anything you have to do for this file.
> After you have applied your changes, but before you restart your
> network service, run this command:
> sudo resolvconf -u
> This will run the script and update your /etc/resolv.conf file. This
> apparently should happen every time the machine boots.
Thanks Ebsen, as soon a this post appears in the archive I'll link the
wiki to it.
At the momewnt the wiki suggests replacing the symlink with a file.
More information about the support