1. DNS & BIND Chapter 24

2. This Chapter DNS Overview

3. DNS (Domain Name System) maps domain names to IP addresses, and vice versa It reduces the need for humans to work with IP addresses, which, with the introduction of IPv6, are complex BIND (Berkeley Internet Name Domain) is a popular open-source implementation of DNS

4. Overview DNS was specified in 1983 and BIND became part of BSD in 1985 – Each node in the hierarchical DNS database is called a domain and is labeled with a (domain) name – the node at the top of the DNS hierarchy is called the root node or root domain

5. The DNS / BIND Hierarchy Pg. 775 in text

6. Reading the Hierarchy A fully qualified domain name (FQDN) is the DNS equivalent of a file system’s absolute pathname: It is a pointer that positively locates a domain on the Internet.

7. The Resolver / Server Relationship The resolver - turns an unqualified domain name into an FQDN that is passed to DNS to be mapped to an IP address. The resolver always appends the root domain (.) to an unqualified domain name first, allowing you to type www.redhat.com instead of www.redhat.com. (including the trailing period) in a browser.

8. The Resolver / Server Relationship The Resolver passes the DNS request to the Name Server to begin the Process. The Resolver to Name Server communication is called the Recursive Query A recursive query sends a domain name to a DNS server and asks the server to return the IP address of the domain: The server may need to query other servers toget the answer.

9. The Recursive Query

10. The Resolver / Server Relationship If a name resolution request cannot be solved by DNS server it will pass the request on to “upstream servers” – this process is called an Iterative Query The Iterative Query sends a domain name to a DNS server and asks the server to return either the IP address of the domain or the name of the DNS server that is authoritative for the domain

11. The Iterative Query

12. Resource Records Information about nodes (domains) in the DNS database is stored in resource records There are more than 30 types of resource records exist, ranging from common types, such as address records that store the address of a host, to those that contain geographical information

13. Resource Records RecordFunction AIPv4 Address—Maps a domain name to the IPv4 address of a host AAAAIPv6 Address—Maps a domain name to the IPv6 address of a host CNAMECanonical Name—Maps an alias or nickname to a domain name. PTRPointer—Maps an IP address to a domain name and is used for reverse name resolution NSName Server—Specifies the name of the system that provides domain service (DNS records) for the domain SOAStart of Authority—Designates the start of a zone. Each zone must have exactly one SOA record. An authoritative server maintains the SOA record for the zone it is authoritative for

14. Installing DNS Install the following packages: bind bind-utils (provides dig among other utilities) system-config-bind (optional) bind-chroot (optional)

15. Starting and Checking the Service Run chkconfig to cause named to start when the system enters multiuser mode: # /sbin/chkconfig named on After you have configured named, start it with service: # /sbin/service named start Named is the name of the DNS daemon

16. System-Config-BIND

17. Adding Zones

18. Adding Records

19. Summary DNS uses a hierarchical method for resoling Host names Recursive queries involve the Client/Server Iterative queries involve the Server/Server Linux DNS requires the manual create of records System-config-bind is the utility for viewing DNS in GUI form

20. Excercise Ensure your system has a statically assigned IP Install DNS Add CNAME records for machines called Chicago, Denver, Atlanta, and Vancouver using your static IP (it will be fine that they all have the same IP Try to use the ping utility to ping these machines by name