Date: Fri, 17 Mar 2006 11:20:29 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Julian Elischer <julian@elischer.org> Cc: freebsd-hackers@freebsd.org, joerg@britannica.bec.de Subject: Re: [RFE] dhclient(8) should send hostname Message-ID: <20060317192029.GB10869@odin.ac.hmc.edu> In-Reply-To: <441B09DA.1010902@elischer.org> References: <200603171502.k2HF2IV3086523@pinky.frank-behrens.de> <20060317151220.GA26987@britannica.bec.de> <441B09DA.1010902@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--8GpibOaaTibBMecb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 17, 2006 at 11:11:22AM -0800, Julian Elischer wrote: > joerg@britannica.bec.de wrote: >=20 > >On Fri, Mar 17, 2006 at 04:02:17PM +0100, Frank Behrens wrote: > >=20 > > > >>I propose a change, that dhclient sends always the current hostname=20 > >>to the server, the value can be overwritten in dhclient.conf. I see=20 > >>no negative impact, because the server has always the possibility to=20 > >>reject the name and to choose another one. It would simplify the=20 > >>setup and lead to the same behaviour as in other (operating) systems. > >>A possible (I'm sure not the best) solution I appended as attachment.= =20 > > > >I object this, since it is one of the most annoying default behaviours > >of Windows. It is the first thing I disable on all clients -- I have a > >static name mapping, why should I update the DNS zone? > > > >Quite frankly, I wouldn't be surprised if the number of zones where the > >host update request is ignored far outweights the number of > >configurations where it is wanted. At least Bind sometimes like to whine > >about it. >=20 > it would certainly make life easier sometimes. I'm inclined to add this feature, possibly with an option to turn it off. It seems like a useful default and it's what other OSes do. I don't believe the objection above has much relevance since the actual update if any is only performed if the DHCP server is configured to make one. Incorrect DHCP packets sent by DHCP servers are my problem. Side effects caused by misconfiguration is not. The actual patch leaves a bit to be desired in that it uses a magic value for the array size and uses sysctl rather than the perfectly adequate POSIX gethostname(). -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --8GpibOaaTibBMecb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEGwv8XY6L6fI4GtQRAvYsAJ9DdUwKkCqpXjqmK4QMHtQ8c8msigCaA5HK K8ymbd6IQcWxuMXuqrUEsuc= =xgU/ -----END PGP SIGNATURE----- --8GpibOaaTibBMecb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060317192029.GB10869>