must be preserved. Files in the slave zone
must be preserved. Files in the slave zone aren’t exactly garbage, but their loss is no big deal. If you expect to serve thousands of domains, you might want to divide your master zone files still further. I use a set of 36 directories under the master directory, one for each letter and number. Of course, you can create any arrangement of directories that fits your needs. Just remember that you’re going to either live with this arrangement or go through some annoyance changing it. Taking this to the logical extreme, your zone entry could look like the following: ………………………………………………………………………………………. zone “AbsoluteBSD.com” { type master; file “master/clients/a/absolutebsd.com”; }; ………………………………………………………………………………………. Most people do not need this number of subdirectories, but you could do it if you needed to. Zone Files At this point we have a configuration file that tells named what domains it’s responsible for, and where the files that contain the information on those domains live. But we still need to make those files! Zone files have a rather obscure syntax because, much like sendmail, BIND was assembled by programmers who were more interested in efficiency than ease of use. Unlike sendmail, zone file configuration is not blatantly user-hostile, though some parts of zone files appear inconsistent. To learn how to work with zone files, follow the given examples and you should be all right. And any time you find yourself scratching your head and wondering why they did something a certain way, just remember that you’re digging through the primordial ooze of the Internet. (If DNS were invented today, zone files would probably look very different.) Here’s a simple example of configuring a zone file. FreeBSD includes a shell script to create the localhost file, make-localhost. To create the localhost file, all you have to do is go to /etc/namedb and type this: ………………………………………………………………………………………. # sh make-localhost ………………………………………………………………………………………. And poof! The file localhost.rev appears. We’ll dissect this file as our first example. ………………………………………………………………………………………. ; From: @(#)localhost.rev 5.1 (Berkeley) 6/30/90 ; $FreeBSD: src/etc/namedb/PROTO.localhost.rev,v 1.6 2000/01/10 15:31:40 peter Exp $ ; ; This file is automatically edited by the `make-localhost’ script in ; the /etc/namedb directory. ; v $TTL 3600 w @ x IN y SOA z satariel.blackhelicopters.org. { root.satariel.blackhelicopters.org. ( 282
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Cheap Web Hosting services