Running Your Own Top-Level Domain
Set up your own TLD in BIND for ease of navigation.
If you administer a network that uses private addressing, you’ve almost certainly encountered the disassociated schizophrenia of trying to maintain zone files that properly reflect internal and external IP addresses. With the introduction of Views in Bind 9, supporting multiple address ranges in a single domain has been significantly streamlined.
While using views is one way to attack the problem, consider the ease
of setting up your own top-level domain. Normally,
zone entries in
named.conf look something like this:
zone "oreillynet.com" {
type master;
file "data/oreillynet.com";
};This is an entry appropriate for an authoritative DNS server for the
oreillynet.com subdomain. The actual top-level
domains (i.e., .com,
.net, .org,
.int, etc.) are only delegated to the mysterious
13 known as the root DNS servers. Even though your servers
won’t be consulted by the rest of the Internet, it
can be handy to set up your very own TLD that works only on your
local network.
For example, suppose you have a group of machines that use the private 192.168.1.0/24 network. These machines aren’t directly reachable from the Internet, and you don’t really want to advertise their DNS information to would-be network crackers. Try a non-standard TLD:
zone "bp" {
type master;
file "data/bp";
allow-transfer { 192.168.1/24; };
allow-query { 192.168.1/24; };
};The bp is short for BackPlane—and, more to
the point, the bp