Red Hat Certified Engineer Tutorials
Network Support Services / Setting up a Slave Nameserver
Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
Learn More
Subtitles of the Movie (Red Hat Certified Engineer / Network Support Services / Setting up a Slave Nameserver)
In this video we'll describe the process of setting up the slave DNS nameserver. The steps in this video are similar to those described in the video in setting up the caching nameserver, but require the help of an existing master nameserver. This video just describes the simplest possible configuration. As noted in the RHCE Exam Prep Guide, all you need to do with various services is configure them for basic, and I emphasize basic, operation. This is one key area where what you do on the RHCE Exam varies somewhat from real life, as job requirements often go beyond basic operation, so we cover just a very few of the rich variety of directives for configuring DNS. If you haven't configured a master DNS server on your system and have a connection to an ISP, you may be able to use their nameserver as a master. Of course, this assumes the policies of your ISP allow you to do so, and this should only be on a temporary basis. The simplest template available for a regular or slave DNS server is in the named dot caching dash nameserver dot conf configuration file. As discussed in the related video we copied that file first to the etc slash named dot conf file, and we updated it to listen to addresses on my local network. We also opened the Firewall in tcp and udp ports 53. Now, to make this work for a master or a slave server, I need to be able to match clients on the local network and this particular directive includes the contents of this file. The default version of this file is essentially the master nameserver for the local host system. To make this work as a slave or master on the local network you need to add appropriate stanzas for forward and reverse lookups. The slave stanza for forward lookup would look something like this, which would serve if the local network was configured as the example dot org domain with the master DNS server configured on the 192 dot 168 dot 0 dot 1 system. When so configured, the database would be located in the noted location and that's a subdirectory of the var slash name slash chroot slash var slash name directory. This assumes, of course, you've installed the bind dash chroot rpm package. If you choose to include a reverse lookup stanza, it could look something like this. This format, the 0 dot 168 dot 192 dot in dash addr dot arpa, that format corresponds to a 192 dot 168 dot 0 dot 0 network. And that also assumes you have a master DNS server configured on the system with IP address 192 dot 168 dot 0 dot 1. Once that's all configured, let's review the service requirements for basic operation. In other videos, we've installed the required DNS packages. We've checked the requirements associated with SELinux. There's a Boolean directive associated with writing to a master DNS server database, so it doesn't affect a slave DNS server. We've made sure that the service starts the next time you boot Linux, we've configured the service for basic operation, and we've also configured security on the system by allowing traffic through port 53. Of course, you could do more, but those are the basics.
Tutorial Information
| Course: | Red Hat Certified Engineer |
| Author: | Michael Jang |
| SKU: | 33845 |
| ISBN: | 1-934743-47-X |
| Release Date: | 2008-01-18 |
| Duration: | 6.5 hrs / 94 lessons |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 81,350 Video Tutorials (14,200 free)
- Video Available as Flash or QuickTime
- Over 715 Courses
- $30 for One Month Access
- Multi-User Discounts Available
