SUMMARY: Tru64 v5.0 weird resolv response

From: Robert Carsey <rcarsey_at_monmouth.edu>
Date: Sun, 12 Dec 1999 21:54:57 -0500

Thanks to Dr. Blinn for pretty much confirming my suspicions that Tru64 v5.0
interprets hostnames in strict(er) accordance with the various RFCs. Of
course the nslookup program works with broken hostnames because it takes what
you type and just asks the DNS server about whatever string you entered.
However, when you do a local lookup (a program using gethostbyname(), i
assume), it breaks like it should.

I did read the Changes manual that came with v5.0; I didn't see this listed,
but maybe i missed this. Things _should_ be RFC anyway soo..perhaps it
wasn't listed.

Also thanks to Dan Schwartz, Kevin Oberman, and Mandell Degerness.

> > Hello -- this bewilders me a little. I realize that underscores in
> > hostnames are not RFC compliant, but I believe this worked fine in
> > ULTRIX and Tru64 up until at least 4.0F.. The error message is a little
> > vague, so I'm not sure what to make of it. When I put an entry in the
> > hosts file, it is OK.
> >
> > # telnet eps_19ffbb
> > eps_19ffbb: Unknown server error
> > # nslookup eps_19ffbb
> > Server: monnet.monmouth.edu
> > Address: 192.100.64.2
> >
> > Name: eps_19ffbb.printers.monmouth.edu
> > Address: 10.20.1.39
> >
> > # telnet 10.20.1.39
> > Trying 10.20.1.39...
> > Connected to 10.20.1.39.
> > Escape character is '^]'.
> >
> > Lantronix EPS2 Version B3.6/104(990812)
> >
> > Type HELP at the 'Local_5> ' prompt for assistance.
> >
> > Username>
>
> I have a recollection about a change in one of the C libraries that
> "broke" non-RFC compliant host names; if telnet is calling whichever
> of the libraries was involved, and it's not handling the underscore
> correctly, you'd fail the lookup. nslookup probably just takes what
> you type as a raw string and passes it to the name server, which is
> NOT the same as doing a local lookup.
>
> There might be a patch for this -- my recollection is what when it
> was discovered that we had implemented strict RFC compliance for this
> area, and it broke customer systems, I believe someone quickly came
> up with a fix to allow systems to run non-conformant, but I would
> have to go do more research than I should have to do to track this
> down.
>
> Tom
>
> Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation
> 110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698
> Technology Partnership Engineering Phone: (603) 884-0646
> Internet: tpb_at_zk3.dec.com Digital's Easynet: alpha::tpb
> ACM Member: tpblinn_at_acm.org PC_at_Home: tom_at_felines.mv.net
>
> Worry kills more people than work because more people worry than work.
>
> Keep your stick on the ice. -- Steve Smith ("Red Green")
>
> My favorite palindrome is: Satan, oscillate my metallic sonatas.
> -- Phil Agre, pagre_at_ucsd.edu
>
> Yesterday it worked / Today it is not working / UNIX is like that
> -- apologies to Margaret Segall
>
> Opinions expressed herein are my own, and do not necessarily represent
> those of my employer or anyone else, living or dead, real or imagined.
>
Received on Mon Dec 13 1999 - 02:56:49 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:40 NZDT