From owner-freebsd-hackers  Tue Nov 26 21:16:37 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA27314
          for hackers-outgoing; Tue, 26 Nov 1996 21:16:37 -0800 (PST)
Received: from netrover.com (ottawa14.netrover.com [205.209.19.23])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA27309
          for <freebsd-hackers@FreeBSD.org>; Tue, 26 Nov 1996 21:16:33 -0800 (PST)
Received: (from brianc@localhost) by netrover.com (8.8.2/8.8.2) id AAA05205; Wed, 27 Nov 1996 00:15:32 -0500 (EST)
Message-ID: <Mutt.19961127001532.brianc@netrover.com>
Date: Wed, 27 Nov 1996 00:15:32 -0500
From: brianc@netrover.com (Brian Campbell)
To: freebsd-hackers@FreeBSD.org
Subject: libc
X-Mailer: Mutt 0.51
Mime-Version: 1.0
Reply-to: brianc@pobox.com
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

There have been a number of people who've noticed it's not a good idea
to link libc.3 and libresolv.2 together in an application.  irc, for
example either just faults or fails to resolve any addresses.  I never
saw anyone reply with reasons why this was so.

Further, it appears that someone (a new RFC?  what number?) decided, in
libc.so.3, that underscores, slashes and who-knows-what-else are invalid
characters in DNS.  So a lot of time gets wasted (on traceroute or
netstat) resolving names that the resolver code in libc will refuse to
display.

Has anyone bothered to tell sprintlink or mci of this "change"?