Some TCP/IP software includes DNS as part of its product. For example, Process Software Corporation's TCPware product includes DNS in its Domain Name Services as a base product feature. Most commercial UNIX vendors include the BIND (Berkeley Internet Name Domain) implementation.
If you’re interested in getting the newest BIND source code, it's available to DNS-registered hosts by anonymous FTP at FTP.UU.NET (address 126.96.36.199) in the directory /networking/ip/dns/bind.
The host system administrator’s responsibilities to maintain the domain are to:
The domain administrator’s responsibilities are to:
You can set up a domain name for your organization and specific networks and hosts within it only after you:
According to RFC 1034, once you choose a name for a zone you administer, you should be able to demonstrate that you have a primary and at least one secondary master. A server doesn't need to be on a host with a name in that domain. In fact, it's best if at least one server is outside the domain.
For some guidelines on setting up a domain, see RFC 1032, Domain Administrator's Guide, or RFC 1033, Domain Administrator’s Operations Guide, available on the Internet.
Suppose you want to set up a domain for the PLATO.PROCESS.COM network of hosts. A good starling point is the root name server for the domain (you are not alone: users query “roots” an average of almost 400 times a second over the Internet). You can go to the root using the nslookup utility, which extracts information from DNS servers:
nslookup > root Default Server: ns.internlc.net Address: 188.8.131.52
Look for name servers in the PROCESS.COM. domain (note the dot at the end of process.com. to make the domain name fully qualified and not relative to your local domain):
> set type=ns ; set the type to Name Server > process.com. Server: ns.in.ternic.net Address: 184.108.40.206 Non-authoritative answer: process.com nameserver = BU.EDU process.com nameserver = SIRIUS.process.com process.com nameserver = NIC.NEAR.NET Authoritative answers can be found from: BU.EDU internet address = 220.127.116.11 SIRIUS.process.com internet address = 18.104.22.168 NIC.NEAR.NET internet address = 22.214.171.124
You can then query one of the name servers listed, such as SIRIUS.PROCESS.COM. Each domain name field is a label that can range from 0 to 63 bytes (known as octets to DNS), although the shorter the label the better. In fact, 12 characters is a suitable maximum. Each label must start with a letter and can be followed by alphanumeric characters (a to z, A to Z, or 0 to 9), or hyphens. Labels end with an alphanumeric character. Although labels aren't currently case-sensitive, case could matter on the Internet some time in the future.
You can theoretically have up to 127 labels (that is, levels) in a domain name, although this would be highly impractical.
According to RFC 1034, “when assigning a domain name for an object, the prudent user will select a name which satisfies both the rules of the domain system and any existing rules for the object, whether these rules are published or implied by existing programs.”
You can query your network address using the whois utility to find out if the network address is registered. For example:
whois -h rs.internic.net 192.42.95 Process Software Corporation (NET-PSC) 959 Concord Street Framingham, MA 01701 Netname: PSC Netnumber: 126.96.36.199 Coordinator: Volz,Bernard (BV15) VOLZ@PROCESS.COM (508) 879-6994 Domain System inverse mapping provided by: SIRIUS.PROCESS.COM 188.8.131.52 NIC.NEAR.NET 184.108.40.206 BU.EDU 220.127.116.11 Record last updated on Ol-Jul-94.
If you’re not registered, use anonymous FTP to access rs.intemic.net (address 18.104.22.168) and copy the /template/internet-number-template.txt file for instructions.
The best way to register with your parent is to contact the domain “coordinator,” like the one listed in the previous example. There are various registration forms available, or you can send the information to the coordinator in an e-mail message.
You need to supply the names and addresses of your domain name servers. In some cases, these should already be operational.
You can register your reverse mapping domain names in the in-addr.arpa domain by anonymous FTP to rs.internic.net (address 22.214.171.124). Follow the instructions in the /template/in-address-template.txt file.
You also have to set up information locally for reverse mapping and other information you should keep in the DNS database on your name servers. These local maintenance issues are covered in the next chapter.
Each TCP/IP software product has its own way of configuring a DNS client resolver and servers. In TCPware's case, for example, your host can support a DNS client only, or both a client and a name server. The TCPware setup procedure prompts you to specify the internet addresses of up to three name servers the client can query.