DHCP client error: domain_not_set.invalid

[Mark Andrews]

> 
> --61jdw2sOBCFtR2d/
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> On Sun, Nov 13, 2005 at 07:14:00PM -0800, Mark Space wrote:
> > Hi all,
> >=20
> > I just set up the latest 6.0 release, and I'm getting errors with the=20
> > DHCP client.  Trying to pull a network address during start up, I get:
> >=20
> > Bogus domain search list 15: domain_not_set.invalid
> >=20
> > This repeats several times before giving up.  Google tells me that this=
> =20
> > problem was report by two users on the bsd-current list.  No one ever=20
> > replied to their inquiries (at least on the list), so I thought to try=20
> > once more to see if there's any interest in addressing this issue.=20
> >=20
> > More info was in the original post:
> > http://lists.freebsd.org/pipermail/freebsd-current/2005-October/057034.ht=
> ml
> 
> We should really bitch and then ignore this value when it's bogus rather
> than rejecting the lease.  We should also probably allow underscores
> since they are popular among clueless Microsoft admins.  Please try the
> follow patch.

	Yes.  They are clueless.  However giving into their cluelessness
	just perpetuates the cluelessness.

	Underscores have never been legal in hostnames.  Underscores
	are deliberately used to provide namespaces which do not collide
	with the hostname namespace.  Accepting underscores just allows
	the namespaces to collide.

	Mark
 
> -- Brooks
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org