In this hands-on project, you configure and test the DNS daemon. 1. Switch to a command...

In this hands-on project, you configure and test the DNS daemon.

1. Switch to a command-line terminal (tty2) by pressing Ctrl+Alt+F2 and log in to the terminal using the user name of root and the password of secret.

2. At the command prompt, type yum install system-config-bind and press Enter to install the graphical BIND configuration utility. Type y and press Enter when prompted to continue the installation.

3. Switch to the gdm by pressing Ctrl+Alt+F2 or Ctrl+Alt+F7 and log in to the GNOME Desktop Environment as sample user one, with the password of secret.

4. Once the GNOME Desktop Environment has started, open a BASH shell terminal, type system-config-bind& and press Enter. When prompted to supply the root user’s password, type secret and click OK.

5. Highlight DNS Server and click Properties. Add the forwarders option to the Current Options box. Highlight IPV4 Address and supply the IPv4 address of your classroom DNS server for this option and click OK when finished. Click OK to close the DNS server property window. This configures your DNS server to forward requests to the classroom DNS server if it cannot resolve the destination address using the information within its own zone files.

6. Click New, Zone and accept the default zone scope of Internet by clicking OK underneath the Class drop-down box. Next, accept the default zone type of Forward by clicking OK below the Origin Type drop-down box and type the zone name class.com. (taking care to include the trailing . in the zone name). Accept the default DNS server zone role of Master (Primary) by clicking OK.

7. Examine the default SOA record parameters. What is the default minimum TTL? Briefly explain what this setting does. Click OK to return to the BIND configuration utility window.

8. Expand your class.com zone. What default records are created in this new zone?

9. Highlight the class.com zone and click New, A IPv4 Address. Type gateway.class.com. in the Domain Name dialog box (taking care to include the trailing . in the FQDN) and supply the IPv4 address of your classroom’s default gateway. Click OK to create the A record.

10. Highlight the class.com zone and click New, A IPv4 Address. Type server1.class.com. in the Domain Name dialog box (taking care to include the trailing . in the FQDN) and supply your computer’s IPv4 address. Click OK to create the A record.

11. Highlight the class.com zone and click New, CNAME Alias. Type alias.class.com. in the Domain Name dialog box and type server1.class.com. in the Canonical Name dialog box (taking care to include the trailing . in both FQDNs). Click OK to create the CNAME record.

12. Highlight the class.com zone and click New, MX Mail Exchange. Note the default domain of class.com. in the Domain Name dialog box and type server1.class.com. in the Mail Server Name dialog box (taking care to include the trailing . in the FQDN). Click OK to create the MX record.

13. Expand your class.com zone. Are the new records visible?

14. Expand the zone that represents your classroom network. Are PTR records available for reverse lookups?

15. Click Save. Click OK when prompted to save your changes to the configuration files on the hard drive. Log out of the GNOME Desktop Environment.

16. Close the BIND configuration utility and switch back to tty2 by pressing Ctrl+Alt+F2.

17. At the command prompt, type service named start and press Enter to start the DNS name daemon.

18. At the command prompt, type chkconfig --level 5 named on and press Enter to ensure that the DNS name daemon is started when the system enters runlevel 5.

19. Edit the /etc/resolv.conf file with a text editor and remove any existing nameserver lines. Add the line nameserver 127.0.0.1 to ensure that your Linux computer uses the local DNS server daemon for name resolution. Save your changes and quit the editor when finished.

20. At the command prompt, type ping –c 4 gateway.class.com and press Enter. Was the name resolved successfully? Explain.

21. At the command prompt, type ping –c 4 server1.class.com and press Enter. Was the name resolved successfully? Explain.

22. At the command prompt, type ping –c 4 alias.class.com and press Enter. Was the name resolved successfully? Explain.

23. At the command prompt, type ping –c 4 www.yahoo.com and press Enter. Was the name resolved successfully? Explain.

24. At the command prompt, type dig @localhost class.com ANY and press Enter. Are your resource records returned successfully?

25. At the command prompt, type less /var/named/chroot/etc/named.conf and press Enter. View the entries. Is class.com a master zone? Do you see a line that forwards unknown requests to your classroom DNS server? Press q when finished.

26. At the command prompt, type cat /var/named/chroot/var/named/class.com.db and press Enter. View the entries. Are your resource records present?

27. At the command prompt, type cat /var/named/chroot/var/named/network_ID.db and press Enter where network_ID is your classroom network ID. View the entries. Are PTR resource records present?

28. At the command prompt, type less /var/named/chroot/var/named/named.root and press Enter. View the entries. What do these entries represent?

29. Type exit and press Enter to log out of your shell.