Novell's NetWare IP 2.12 had a DNS subsystem including a name server. It supported MX records and seemed to be fairly functional as a caching server, but did not do zone transfers at that stage. Version 2.2 apparently required the administrator to use a menu system for configuration. More details of the DNS subsystem for NetWare would be welcome.
Ports of old versions of BIND to OS/2 exist, although I'm not aware of any more recent than BIND 8.2.4. Several of these can be found at the hobbes archive.
IBM apparently also provided a name server for OS/2. Further details would be welcome.
IBM had a name server implementation in their TCP/IP for VM and MVS. Craig Jackson mentioned that the name server in the mainframe TCP/IP product is not based on BIND but on software developed in the mid-80's at the University of Wisconsin, and uses a relational database backend. It is not known if these products are still available.
TGV Multinet included an enhanced VMS port of BIND. Craig Jackson mentioned that the TGV port (as of 1996) ran under TGV's superserver and was heavily multithreaded. This software is now under the banner of Process Software. Jeff Schreiber from Process Software stated that their TCPware DNS server was a VMS port of BIND, with added features such as cluster load balancing. According to Dave Barlow from Process Software, The code base for MultiNet V4.1 is BIND 4.9.7 while later versions are based on BIND 8.
http://www.process.com/openvms.htp http://www.process.com/multinet/
Paul Vixie mentioned that DEC's VMS TCP/IP implementation had a name server not based on BIND.
Brad Knowles reported using Wollongong TCP-IP under VAX/VMS; apparently the work was originally done by TGV and was based on BIND.
The KA9Q suite of DOS communications software contains a DNS server.
ftp://ftp.demon.co.uk/pub/demon/ibmpc/dos/files/
Steve D. Miller pointed out that the NetManage ChameleonNFS 4.0 manual stated that the product included a DNS server. It seems it only did hostname to IP translation. Later versions of NFS/X were released, but no details about the functionality of the included name server are available.
A package called "bind" was available from FTP Software under MS-DOS. This was discontinued several years ago.
Banyan shipped a DNS server. According to Merton Campbell Crockett, FTP Software provided the original TCP/IP support for Banyan VINES.
Roland Schemers implemented lbnamed,
a load-balancing DNS forwarder, at Stanford and presented a paper
on it at the LISA IX conference in September 1995.
lbnamed is implemented as a Perl script, and strictly
speaking is not a server but a server adjunct.
This idea is now widely used by vendors of commercial load balancing
appliances and other network hardware, though in contrast to
lbnamed, some black-box trickery is involved and source
code is generally not available.
The Perl module Stanford::DNSserver
is a recent further development of lbnamed, by Rob Riepel
and several contributors.
Simon Leinen came up with a real exotic:
The DNS server in Genera, the operating system of the Symbolics Lisp Machines. It is written in Lisp (of course). The source is about 750 lines long.
Richard Shuford sent information on the md-dns name server which ran on VOS for Stratus fault-tolerant computers, but appears to have been discontinued.
Back to Name Server Software index or DNSRD.