12.04 not set nameserver in pxe boot ( resolvconf or dhcp client bug)

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/946215/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Hello and thanks for the report.

What version of the resolvconf package do you have installed? What is the date of your Precise image? Can you please provide your /etc/network/interfaces file?
--
Thomas Hood

I use the daily build iso of 12.04 in date 2012-03-03.
The problem is in live run, in fact the install procedure is not able to connect to take upgrade and language packages . I resolve with :echo "nameserver 192.168.0.1">> /etc/resolvconf/resolv.conf.d/base; resolvconf -u.
The nameserver was the olny bad setting. Ip address and gateway were automatically configured.
After install i must change /etc/network/interfaces file because eth0 was set to manual (not to dhcp).
The last problem is also present after the installation of 10.04.4 . ( instead in 10.04.4 live the dns is set correctly )

What tools have you used to prepare the pxe image? How did these tools handle populating /etc/resolv.conf prior to 12.04?

It's likely that these tools need updated to work with resolvconf.

It seems that the Precise 2012-03-03 live image uses resolvconf to manage /etc/resolv.conf but the DHCP client in the installer on the live image does not send its nameserver information to resolvconf. If that's true then this report should be reassigned.
--
Thomas

The DHCP client in the live environment is Network Manager and it definitely talks to resolvconf just fine.

Tracked it down to 23networking in casper writting /etc/resolv.conf in the target which obviously won't quite work because of resolvconf.

I'll do some copy/pasting of the code I wrote for LTSP in a similar use case.

This bug was fixed in the package casper - 1.306

---------------
casper (1.306) precise; urgency=low

  [ Sergey "Shnatsel" Davidoff ]
  * Comment on the recently-introduced FLAVOUR variable in casper.conf.

  [ Stéphane Graber ]
  * in 23networking, when writing resolv.conf detect resolvconf and write
    to /run/resolvconf/interfaces/casper instead. (LP: #946215)
 -- Stephane Graber <email address hidden> Mon, 05 Mar 2012 15:38:23 -0500