[Bug 1013843] Re: resolv.conf empty when doing PXE installations
Daniel Manrique
daniel.manrique at canonical.com
Mon Jun 18 14:33:48 UTC 2012
Hi Thomas,
A few of the files you requested weren't in /run, here's the output of
the commands you requested (I put them all in one script):
# bash script.sh
total 4
-rw-r--r-- 1 root root 0 Jun 18 09:53 enable-updates
drwxr-xr-x 2 root root 40 Jun 18 09:53 interface
-rw-r--r-- 1 root root 151 Jun 18 09:53 resolv.conf
total 0
=== /run/resolvconf/interface/* ===
cat: /run/resolvconf/interface/*: No such file or directory
=== /etc/resolvconf/resolv.conf.d/base ===
=== /etc/resolvconf/resolv.conf.d/head ===
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
cat: /run/nm-dns-dnsmasq.conf: No such file or directory
The remaining file you requested /etc/resolv.conf has nothing but the
comment as seen in the original report:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
Please let me know if you need more information about this problem.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1013843
Title:
resolv.conf empty when doing PXE installations
Status in “resolvconf” package in Ubuntu:
New
Bug description:
Quantal daily image as of 20110615.
resolvconf 1.65ubuntu4.
In our environment we do network installs via PXE booting. We noticed
that name resolution wasn't working during the late_command phase
(e.g. any apt-get install operations in the ubiquity/late_command
fail).
PXE passes IP information (including DNS) to the kernel, and in this
case, the entry in /etc/network/interfaces is:
auto eth0
iface eth0 inet manual
What we found is that, with this configuration, /etc/resolv.conf will
be unconfigured (even though DHCP *did* send DNS information):
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
if I change the /etc/network/interfaces entry to
auto eth0
iface eth0 inet dhcp
then I run:
sudo ifup --force eth0
then /etc/resolv.conf is populated correctly and DNS resolution starts
working.
This would be a regression from Precise, where the resolv.conf file
gets correctly populated even if the interface is set as manual.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1013843/+subscriptions
More information about the foundations-bugs
mailing list