Setting Up a Slave Perhaps the easiest task
Setting Up a Slave Perhaps the easiest task in DNS is to set up a slave domain. The entry will look much like the entries for the root zone and the localhost zone. You need to know the name of the domain you want to slave, and the IP address of the master nameserver. To set up a slave domain, copy the localhost zone entry and change it slightly. The configuration for the slave server for http://absolutebsd.com/, for example, looks like the following, which closely resembles the root and localhost zones. ………………………………………………………………………………………. v zone “AbsoluteBSD.com” { w type slave; x file AbsoluteBSD.com.db; y masters {209.69.178.18;}; } ……………………………………………………………………………………………….. We have the domain name (v), a label for the type of zone it is (w), and a filename (x). The filename is where the information for the domain is kept. It’s traditional in DNS to give these files the same name as the domain, with a “.db” extension. (Despite what the extension might imply, these files are in no way databases.) This file will be created when the slave downloads the domain data from the master. We then have the IP address of the master server (y). The slave will request the domain’s DNS information from the master at regular intervals. (We’ll see what sort of intervals later.) The master nameserver must be listed by IP address; after all, the DNS server must be able to bootstrap its records before it knows the IP of anything! Setting Up a Master The named.conf configuration you need when you want a server to be a master is even simpler than the setup for a slave zone: ………………………………………………………………………………………. v zone “AbsoluteBSD.com” { w type master; x file AbsoluteBSD.com.db; } ………………………………………………………………………………………. Once more there’s the domain name (v), a label for the type of zone it is (w), and a filename (x). Unlike a slave domain, you’ll have to create this file. We’ll look at how to create that file in the “Zone Files” section. Setting Up Multiple Zones If you’re managing high-end Internet nameservers, you may be responsible for thousands of domains. If you screw up, you will have a lot of people very angry with you. Therefore, before you set up hundreds of zones, think about how you’re going to arrange them. One thing that can make your life easier when setting up multiple zones is to divide a server’s zone files between those that the server is the master for and those that the server just backs up. I usually do this with two directories, master and slave. Files in the master directory are sacred, and 281
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost PHP Web Hosting services