Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!ucbvax!UMIACS.UMD.EDU!steve
From: steve@UMIACS.UMD.EDU (Steve D. Miller)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Translating names/addresses to human-readable descriptions
Message-ID: <9012130126.AA19266@fnord.umiacs.UMD.EDU>
Date: 13 Dec 90 01:26:35 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19


   Sorry to eat up bandwidth with this, but it seems that lots of people
don't know:  the latest version of BIND (4.8.3, which I suppose is also
known as 4.8.3.1, depending on what you look at) does support TXT records.
The support is not perfect.  However, the protocol-related part of the
support (i.e., the way the bits look on the wire) is right, so far as I
know.

   The MIT Hesiod servers also know about TXT records (and they're even
right now, as a side-effect of the BIND 4.8.3 development effort).  Probably
the UT BIND supports TXT, too, but I haven't looked at it recently...

	-Steve

P.S.:  While I'm cluttering up the net, has anyone implemented for BIND the
new RR types from RFC 1183?  I know about the AFSDB implementation.

Spoken: Steve Miller    Domain: steve@umiacs.umd.edu    UUCP: uunet!mimsy!steve
Phone: +1-301-405-6736  USPS: UMIACS, Univ. of Maryland, College Park, MD 20742