Chapter 17. Berkeley Internet Name Domain (BIND)

Chapter 17. Berkeley Internet Name Domain (BIND)

17.1. Introduction to DNS
17.1.1. Nameserver Zones
17.1.2. Nameserver Types
17.1.3. BIND as a Nameserver
17.2. /etc/named.conf
17.2.1. Common Statement Types
17.2.2. Other Statement Types
17.2.3. Comment Tags
17.3. Zone Files
17.3.1. Zone File Directives
17.3.2. Zone File Resource Records
17.3.3. Example Zone File
17.3.4. Reverse Name Resolution Zone Files
17.4. Using rndc
17.4.1. Configuring /etc/named.conf
17.4.2. Configuring /etc/rndc.conf
17.4.3. Command Line Options
17.5. Advanced Features of BIND
17.5.1. DNS Protocol Enhancements
17.5.2. Multiple Views
17.5.3. Security
17.5.4. IP version 6
17.6. Common Mistakes to Avoid
17.7. Additional Resources
17.7.1. Installed Documentation
17.7.2. Useful Websites
17.7.3. Related Books

On most modern networks, including the Internet, users locate other computers by name. This frees users from the daunting task of remembering the numerical network address of network resources. The most effective way to configure a network to allow such name-based connections is to set up a Domain Name Service (DNS) or a nameserver, which resolves hostnames on the network to numerical addresses and vice versa.

This chapter reviews the nameserver included in Red Hat Enterprise Linux and the Berkeley Internet Name Domain (BIND) DNS server, with an emphasis on the structure of its configuration files and how it may be administered both locally and remotely.

Note

BIND is also known as the service named in Red Hat Enterprise Linux. You can manage it via the Services Configuration Tool (system-config-service).


Note: This documentation is provided {and copyrighted} by Red Hat®, Inc. and is released via the Open Publication License. The copyright holder has added the further requirement that Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. The CentOS project redistributes these original works (in their unmodified form) as a reference for CentOS-5 because CentOS-5 is built from publicly available, open source SRPMS. The documentation is unmodified to be compliant with upstream distribution policy. Neither CentOS-5 nor the CentOS Project are in any way affiliated with or sponsored by Red Hat®, Inc.