resolvconf starts too late, breaks DNS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resolvconf (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
I run Dapper on two machines, one with a PCMCIA wired network card, and one with a MiniPCI wireless card. On both of them, the /etc/resolv.conf file is empty on bootup (except for the "DO NOT EDIT" comment). This is less than useful.
The problem is that resolvconf somehow initializes after dhclient has already been run. This overwrites the dhclient-generated resolv.conf with a blank version.
If I tell resolvconf to start earlier, by moving /etc/rcS.
Changed in resolvconf: | |
status: | Unconfirmed → Confirmed |
Changing Severity to Critical, because this makes the system useless for anyone who doesn't know how to restart the network.