Bug#236533: #236533: dhcp-client: support for Dynamic DNS in netcfg

[Frans Pop <aragorn@tiscali.nl>]

On Friday 28 May 2004 19:16, Joshua Kwan wrote:
> OK. Were you indeed asked for a DHCP host name?

Yes.

> Oh, I see. You can't give a DHCP hostname if DHCP works the first time.
> I guess the way to resolve this is to kick $DHCP_CLIENT in the shins
> with a hostname and acquire a new lease right after specifying your
> hostname, so that the send host-name parameter takes.

Yes, that would solve it. But where is the 'send host-name' parameter set 
currently? I don't see it in the dhclient.conf that is currently generated by 
netcfg.

> It's all about balancing user requests. This could also be fixed by
> asking for a hostname first, but then we lose the ability to use
> seed_hostname_from_dns or DHCP server-given hostnames.
>
> I wonder if there's a better way to do this. Alternative right now is
> also to always ask the dhcp_hostname question first if prio is medium,
> and that's fairly easy to code.

Personally I don't really care if I have dynamic DNS the first time (during 
1st stage installation). I can't really think of a reason why it would be 
important.
I just feel it should be set up correctly for after the reboot.

After the reboot, I _do_ have a hostname, but it isn't being sent to the 
server as part of the DHCP request.

Up to now I've always solved this by manually adding a line
   send host-name "<hostname>";
to dhclient.conf after the installation.
As far as I can tell, this is needed for both dhcp and dhcp3.

> > Also, I was asked to provide a domain name during netcfg, even though the
> > domain name is provided by my DHCP server.
>
> Fixed in trunk, thanks. (I think.)

Thanks. (I hope ;-)