Ubuntu
resolvconf package

/etc/init.d/resolvconf start is run too late, clobbering resolv.conf information

Bug #595886 reported by jwm
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: resolvconf

In the brave new world of upstart event driven start up both /etc/init.d/networking and network-manager based net connections can, and typically do, come up before the usual SysV init scripts are run, such that running /etc/init.d/resolvconf start ends up flushing the DNS information out of resolv.conf.

Per session solution:

sudo restart network-manager
or;
sudo service networking restart

Per upgrade work around:

sudo update-rc.d -f resolvconf remove

Long term solution:

Running service resolvconf start from upstart before networking is started. Not sure how to do this.

Revision history for this message
jwm (jwm-angrymonkey) wrote :

Applies to karmic and lucid versions of resolvconf.

Thomas Hood (jdthood)
summary: - /etc/init.d/resolvconf start clobbers resolv.conf information
+ /etc/init.d/resolvconf start is run too late, clobbering resolv.conf
+ information
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.