[Bug 1013843] Re: resolv.conf empty when doing PXE installations

Daniel Manrique daniel.manrique at canonical.com
Tue Jun 19 15:09:57 UTC 2012


Hi Thomas,

For your suggestion on comment #7, note that the "iface eth0 inet
manual" stanza was added automatically by casper as a result of
netbooting, thus I don't really have an opportunity to add the dns-
nameservers entry prior to the system booting.

I could do it in one of three places:

- Somehow hacking casper's scripts/casper-bottom/23networking file to
add the dns-nameservers entry and rebuilding the initrd with this
modified casper.

- Manually, by jumping to a console and editing the file by hand. But
I'd still have to ifup the interface for the changes to take effect.

- Automatically, in my preseed file, possibly in the late_command or in
one of the early_commands. Again, I probably would have to somehow
reconfigure the interface for the changes to be considered.

I'll try the manual option (second one) to see which results this
workaround yields and update again. 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
Status in “ubiquity” 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