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.
In this video we'll configure a DNS caching nameserver. The default files associated with the caching nameserver rpm are sufficient. This video assumes the package is already installed with any dependencies. The caching nameserver rpm includes say etc named dot caching dash nameserver dot conf configuration file. We'll copy that to the etc slash name dot conf file, which is the main configuration file for DNS, but before we do that, let's back up any existing version of that file. Just in case something goes wrong. I back it up to the root user's home directory. You can back it up to the directory of your choice. Okay, now let's take a look at this file. Note the directives that look at port 53. The server listens on port 53, it also makes queries on port 53, so later in this video, we'll open up the Firewall in port 53 to make this DNS server good for other systems on the network. But what other systems? Right now, this just listens to the localhost system, also known in IPv4 as address 127 dot 0 dot 0 dot 1. I'm going to set it up for my own local IPv4 network. Note how I use sider notation for this purpose. Don't forget the semi colon. Okay, that should work. Now, let's activate this caching nameserver. The DNS script is available in the etc slash init dot d directory. If the system is already running, you may want to run the restart command. If it works, we'll see a series of messages to that effect in the var slash log slash messages file. And we have a series of log messages associated with the name daemon, which seem to indicate success. Yeah, we have this little problem associated with the winbind service, which is associated with the windows Internet name service, but if you're not running wins or Samba at all that's not a problem. Next, let's make sure DNS is activated at appropriate runlevels, so your change will survive a reboot and they can be properly graded during your exam. Right now DNS is set to start in norunlevels. The easiest way to get it starting in appropriate runlevels is with the chkconfig named on command, and now it's set to start when you boot into runlevels 2, 3, 4, or 5. Now, let's set up the Firewall. Just for variety , we'll do this from the Firewall. The Firewall is enabled and we customize it to allow access to port 53 using the tcp and udp protocols. Why both tcp and udp? Because it's so listed in the etc slash services conf file. Now, let's test this DNS server. First, let's connect to a remote system. And in another video, I described how you could use the dig command to test the DNS server. The local system or the system where I created the DNS caching nameserver is on 192 dot 168 dot 0 dot 40. And let's see what it gives when I look up vtc dot com. That looks like a good DNS server. Now that you've verified that the DNS server works and is properly configured, you can update the resolv dot conf configuration files on any clients that you want to use the server. Alternatively, you could update a DHCP server to provide this information, but remember, such an update wouldn't necessarily apply to clients with static IP addresses.
| 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 |