How NSAP-capable DNS servers deployed?

[[e-mail]]

Folks,

I'm trying to get some idea of how many deployed DNS servers support
name->NSAP mapping according to draft-manning-dns-nsap-03.txt.  If
you're currently doing so (or have plans to do so in the fairly near
future) I'd appreciate it if you'd drop me a note with the relevant
domain name and status.

--Richard

P.S. - I've attached info on how to get the NSAP-capable Bind implementation.
       If there are other questions about this feel free to ask.




----- Begin Included Message -----

>From [e-mail] Mon May 17 14:00:13 1993
Date: 17 May 1993 10:59:51 -0700
>From: Paul Traina <[e-mail]>
Subject: BIND 4.9 with NSAP support
To: [e-mail]
Cc: [e-mail]
Content-Transfer-Encoding: 7BIT
Content-Length: 3065

Diffs for BIND 4.9(beta) to support NSAP addresses are available from
ftp.cisco.com:/ftp/bind/4.9-nsap-diffs

Also available are diffs for 4.8.3, but these are nasty, unsupported, 
not completely functional, and if you've never done a 4.8.3 for your
platform, just don't screw with them.  BIND 4.9 is a -major- win and
installs w/o hacking on a number of platforms.

ftp.cisco.com:/ftp/bind/4.8.3-nsap-diffs

Please remember, we run a special ftp daemon that does not allow you to put
pathnames in your requests.

ftp ftp.cisco.com
anonymous
fnord
cd bind
get 4.9-nsap-diffs

These patches will give you a working DiG, nslookup, resolver libraries,
and a server.  They are compatible with the NCSA TUBA-Telnet and cisco
client implementations.

The patches are a joint effort between Richard and myself.
Bug reports to me, please.

Paul


------- Forwarded Message

Message-Id: <[e-mail]>
To: [e-mail], [e-mail]
Subject: BIND 4.9 has been released
Date: Mon, 17 May 93 03:20:55 -0700
>From: Paul A Vixie <[e-mail]>
X-Mts: smtp

After several years of development and at least one year of testing, BIND 4.9
has finally exited Beta testing and is ready to rock and roll.  You can get it
from gatekeeper.dec.com via anonymous FTP as /pub/BSD/bind/4.9/4.9.930517.tar.Z
(the Bind Operations Guide, substantially improved, is in the same directory,
called BOG.psf).

This BIND has been the name server running on DECWRL.DEC.COM, UUNET.UU.NET, 
EUNET.EU.NET, MUNNARI.OZ.AU, and hundreds of other large and small servers,
for at least six months.  We consider it "stable".

Improvements over 4.8.3 are too numerous to list.  If you have had any kind of
trouble with 4.8.3 (and if you use it, you've had trouble with it, though you
may not know this), you should upgrade to 4.9.  Operating system vendors are
encouraged to include this version of BIND as soon as their release schedules
permit; the NSFnet backbone will thank you for it, as will your customers.

This BIND includes "dig" (from USC/ISI) and "host" (from Rutgers), as well as
a large collection of contributed scripts, utilities, and documentation.  The
resolver has also been improved.

This BIND is known to compile and run on ULTRIX/RISC 4.2-4.3, SunOS 4.1.x,
BSD/386 1.0, NeXTstep 3.0, UMIPS/V, HP-UX 8.x, Alpha AXP OSF/1 1.2, and more.

This BIND was funded by Digital Equipment Corporation and is hereby released
into full public use, subject to the same restrictions as the U C Berkeley
Networking 2 ("net2") release.  There is a DIGITAL ("DEC") Copyright in each
file but it's just noise for the lawyers -- no practical restrictions have
been added other than DIGITAL's disclaimer of liability.

I (Paul Vixie) was the principle contributor to this release, as well as code
librarian and test/release coordinator.  However, my efforts would have been
wasted without the assistance and participation of the alpha test list, to
whom special thanks are given in the new Bind Operations Guide ("BOG").

------- End of Forwarded Message



----- End Included Message -----