ISC's BIND site is the home of the latest version of the Berkeley named written and maintained by Paul Vixie. The latest BIND release (8.x) is significantly different from previous versions and now supports IP6! The ISC site contains pointers to even more DNS guides and tools.

Dan Bernstein's DJBDNS is a replacement for BIND. In the tradition of djb tools, djbdns has a number of smaller tools instead of larger self contained programs. The collection of DNS tools includes dnscache, tinydns, walldns, rbldns, a dns library, dnsfilter, nsip, dnsipq, dnsname, dnstxt, dnsmx, dnsq, dnsqr, and dnstrace.

DNS resources directory contains documentation (FAQs, books, mailing lists and newsgroups), server software and tools, and Internic registration templates.

The comp.protocols.tcp-ip.domains FAQ contains answers to questions about utilities to administer dns zone files, definitions, configuration, and troubleshooting.

The Linux Network Administrators Guide gives a good basis for various kinds of network applications such as email, news, UUCP, and TCP/IP and PPP protocols. It has one specific section devoted to BIND and resolver setups and one on NIS and NIS+.

This unofficial BIND FAQ describes has some very basic information on running your own DNS server on UNIX and NT.

Cricket Liu's presentation on how to secure BIND.

O'Reilly's fourth edition of DNS and BIND, and DNS on Windows 2000.

ICANN is the non-profit corporation that was formed to assume responsibility for the IP address space allocation, protocol parameter assignment, domain name system management, and root server system management functions previously performed under U.S. Government contract by IANA and other entities. AMong other things, you can find a list of accredited registrars.

DNS Boss is a commercial Java product available for Solaris 2.5 and above that allows you to rapidly setup and maintain one or many DNS domains via a web-based GUI. DNS Boss integrates well with NIS and NIS+, DHCP, and has an open API which can be used for IP Management.

Dynamic DNS updates are defined in RFC 2136

It's possible to roll your own DDNS server with bind and nsupdate.

A couple lists of DDNS providers:

• highsynth
• technopagan

The goal of the Dynamic DNS Tools Project is to provide an open and free (in the GPL-sense) set of tools that will permit the deployment of secure and reliable dynamic DNS services. The project will use DDT to provide free dynamic DNS service to the public. The service will offer hostnames under the ddts.net domain, where DDTS stands for DDT Service. There are three parts to Dynamic DNS Tools:

1. 1) the DDT client daemon, ddtcd, and the client utility, ddtc
2. 2) the DDT server daemon, ddtd, and the admin utility, ddta
3. the CGI scripts used for web-based account registration and administration.

The Resources for DHCP site has an FAQ that covers some basic networking questions like what IP and MAC adresses are and then delves into information about DHCP, including a brief overview, who created it and how, what protocol it uses, the relationship with BOOTP, and then into the guts of DHCP. The site also includes IETF DHC WGs, RFCs, and various other pointers

ISC's DHCP distribution provides a freely redistributable reference implementation of all aspects of the DHCP protocol, through a suite of DHCP tools: a server, client, and relay agent. The tools all use a modular API which is designed to be sufficiently general that it can easily be made to work on POSIX-compliant operating systems and also non-POSIX systems like Windows NT and MacOS.

DHCP is defined in the following RFCs:

• Specification and options: 2131, 2132
• Interoperation With BOOTP: 1534
• Clarifications and Extensions for the Bootstrap Protocol: 1542
• Options for Novell Directory Services: 2241
• Netware/IP Domain Name: 2242
• The Open Group's User Authentication Protocol: 2485
• Disable Stateless Auto-Configuration in IPv4 Clients: 2563
• Service Location Protocol: 2610
• Name Service Search: 2937
• Procedure for Defining New DHCP Options and Message Types: 2939
• User Class: 3004
• Subnet Selection: 3011
• Relay Agent Information: 3046
• DHC load balancing algorithm: 3074
• Authentication for DHCP Messages: 3118

DHCP mini-HowTo for Linux covers setting up DHCPd/DHCPcd for Slackware, RedHat, and Debian. It attempts to answer basic questions on how to setup a linux box to serve as a DHCP server or a DHCP client.

Cisco DNS/DHCP Manager is a suite of TCP/IP management applications that manage domain names and synchronize IP addresses between a Domain Name System (DNS) server and a Dynamic Host Configuration Protocol (DHCP). The Cisco DNS/DHCP Manager also includes a DNS server, TFTP server, NTP server, and a syslog server.

Network Access Control for DHCP Environment is a paper written by Kazumasa Kobayashi and Suguru Yamaguchi of the Nara Institute of Science and Technology in Japan. The paper proposes a new access control method to be used as the DHCP message authentication mechanism. They designed and developed the DAG (DHCP Access Control Gateway) as an example of the proposed method. The DAG is a gateway program that passes network accesses only by clients with addresses formally allocated from the DHCP server.

DHCP: A Guide to Dynamic TCP/IP Network Configuration, by Berry Kercheval (1999), is a guide to connecting a LAN to the Internet with DHCP. The book covers how DHCP works from both the client's and server's point of view, configuration options, dynamic DNS, ubnet and lease maintenance, integrating DHCP with LDAP, IPv6 and other key Internet-related protocols.

WIDE DHCP is the DHCP implementation that's part of the WIDE (Widely Integrated Distributed Environment) project. The WIDE project, based in Japan, sets its goal as establishing a large-scale distributed computing environment.

O'Reilly's DHCP for Windows 2000.