Planning for DOMAIN name resolution

If you are part of a larger internetwork, coordinate setting up your domain and name servers with the central authority.

• Because of the vast possibilities in architecture and configuration, become familiar with TCP/IP, DNS, and BIND before you solidify any plans. If you plan to use a network information service, become familiar with NFS and NIS as well. Books about these topics are widely available. For more information about NIS and NIS+, see Network Information Services (NIS and NIS+) Guide.
• Plan ahead.

  Changing a name is much more difficult than setting up the initial one. Obtain consensus from your organization on network, gateway, name server, and host names before you set up your files.

• Set up redundant name servers.

  If you cannot set up redundant name servers, be sure to set up slave and hint name servers so you have some type of backup.

• In selecting the name servers, keep the following in mind:
  • Choose machines that are physically closest to exterior systems.
  • The name servers should be as independent as possible. Try for different power supplies and independent cabling.
  • Find another network to back up your name resolution service, and do the same for other networks.
• Test the servers.
  • Test both regular and reverse name resolution.
  • Test zone transfer from master to slave name servers.
  • Test each name server after a system crash and reboot.
• Send name resolution requests to forwarder servers before they go to exterior name servers. This allows your name servers to share caches and improve performance by reducing the load on your master name servers.

objectclass container
        requires
                objectclass,
                cn
objectclass hosts
        requires
                objectclass,
                hname
        allows
                addr
                halias,
                comment