I just ran into this issue recently for a group of hosts I'm managing,
and solved it, for now, by importing the patch "debian/patches/dynamic-
hostname.dpatch" from Ubuntu's DHCP3 package, and adding:
send host-name "<hostname>";
to the default config file. Just to get things going for myself.
However, while investigating things, I ran into good news from
upstream; it looks like it will be (finally!) fixed in dhclient 4.2,
woo!
From http://oldwww.isc.org/sw/dhcp/dhcp4_2.php?noframes=1
"
Added a configuration function, 'gethostname()', which calls the
system function of the same name and presents the results as a data
expression. This function can be used to incorporate the system level
hostname of the system the DHCP software is operating on in responses
or queries (such as including a failover partner's hostname in a dhcp
message or binding scope, or having a DHCP client send any system
hostname in the host-name or FQDN options by default).
"
But, since 4.2 alpha was just released in December, and Debian doesn't
even have 4.1 yet, it looks like this probably won't make it in time
for squeeze...and it'd be really nice if it worked right out of the
box in Squeeze if at all possible.
So, perhaps now that upstream's preferred solution is known, it'd be
okay to backport that change to the DHCP version currently in Debian,
so that squeeze can have the fix? I suspect it *WOULD* be completely
trivial to backport, if ISC's CVS repository wasn't behind a $200 pay-
wall (Seriously!!!!!!!!!). But, even without being able to just merge
the single commit, I think just grepping for expr_gethostname and
copying everything about that is likely to be all that's needed.
If you're amenable to releasing a dhcp3-client with such a backport, I
can take a shot at extracting out such a patch...(although, perhaps
you have access to upstream's source repo and it'd be easier for you?)
James
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
