Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Mar 2003 21:24:09 -0600
From:      David J Duchscher <daved@nostrum.com>
To:        Terry Lambert <tlambert2@mindspring.com>
Cc:        stable@FreeBSD.ORG
Subject:   Re: Resolver Issues (non valid hostname characters)
Message-ID:  <6888D394-5F3A-11D7-90A2-0003930B3DA4@nostrum.com>
In-Reply-To: <3E811499.93BC4550@mindspring.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, March 25, 2003, at 08:46  PM, Terry Lambert wrote:

> Marius Strom wrote:
>> I've submitted a PR for this: misc/50299 documenting the RFC
>> mis-following (is that a word?) as well as a patch for res_comp.c.
>
> Great.
>
> If this is committed before RFC-952 is updated, FreeBSD users
> can now define host names that break other machines on the net
> which are strictly conformant to RFC-952.

Which will just make us behave like rest of the world.  I have tested
resolvers on Solaris, Windows, MacOS X, MacOS 9, IRIX, Linux, AIX.
They all will resolve a name with an underscore character.  Only the
*BSD boxes fail because of the check.

> What is the first maxim of protocol design?
>
> "Be generous in what you accept, strict in what you generate".

Which is why I would argue that the patch should be committed, maybe
with an option to enable it.  We are talking about the resolver, not a
DNS or hostname server.  The resolver should resolve the name, be
generous.  It just depends at what level you apply the maxim.  The
check should be in the DNS server not in the resolver IMHO.

DaveD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6888D394-5F3A-11D7-90A2-0003930B3DA4>