Resolver Issues (non valid hostname characters)

[Maxim M. Kazachek]

On Tue, 25 Mar 2003, Chris Pressey wrote:

>On Tue, 25 Mar 2003 22:51:44 -0600
>David J Duchscher <daved at nostrum.com> wrote:
>
>> I can't talk to some hosts on the internet because FreeBSD will not
>> resolve the host name which over 99% of the host on the Internet will.
>> I guess that just doesn't matter.
>>
>> DaveD
>
>I don't get it.
>
>If I run a non-standard web server, I wouldn't expect to be able to
>serve web pages to standard user agents.
>
>If I use a non-standard host name, why should I expect to be able to
>be reached by standard resolvers?
>
>i.e.  You can't talk to some hosts because their host name is broken.
>The problem is on *their* end, just as if they were running a
>gratuitously incompatible http server.  How is this FreeBSD's fault?
>
>(I must admit I'm a little biased... I can't bring myself to seriously
>believe that a host with an underscore in its name could possibly have
>anything to offer that I'd be interested in...)
>
	Well, I had a lot of practice with Micro$oft Windows' DNS
implementation and I've ran flawlessly with hostnames (and, of course,
NetBIOS names) with underscores... I may say it looks "better" than names
without it or with minus sign... It's MHO, of course... Many of OSes
permit underscore in host names... By the way, why hostname with
underscores can be resolved when it in /etc/hosts, but it can't be
resolved when it in Microsoft's DDNS implementation... Microsoft doesn't
complain about it both on server and client side... To track standard we
must "filter" those hosts in ANY case, I think... We don't... Then we must
do something with this situation, I think...

   Sincerely, Maxim M. Kazachek
       mailto:stranger at sberbank.sibnet.ru
       mailto:stranger at fpm.ami.nstu.ru