| 20010601 ; Serial } 3600 ; Refresh
| 20010601 ; Serial } 3600 ; Refresh ~ 900 ; Retry 3600000 ; Expire j 3600 ) ; Minimum IN NS satariel.blackhelicopters.org. 1 IN PTR localhost.blackhelicopters.org. ………………………………………………………………………………………. First of all, remember that anything that begins with a semicolon is a comment. (Comment your zone files liberally; it’ll help you figure out later what the heck you were doing.) $TTL: Time to Live We’ll skip on through this file to the first line of real interest, the $TTL statement (v). This statement is the zone’s default time to live, in seconds (3,600 seconds, in this case), and it dictates how long other servers will cache information from this zone. You can give data in the zone any time to live you choose. This is actually a fairly short time; a good average is 10,800, or 3 hours. Choosing a TTL is something of a black art; stick with the default, and you’ll be fine for most purposes. Start of Authority Next is the Start of Authority (SOA) record. This is a brief description of the zone, and of how its characters and servers should treat it. Every zone has exactly one SOA record. The SOA does not include information about what is in the domain, merely information about how long this information lasts. The @ sign The at symbol (@), which begins the SOA record (w), is a special character that’s shorthand for “whatever named.conf says this file is for,” and in this case, named.conf says that this file holds data for the zone 0.0.127.in-addr.arpa. When named reads named.conf and loads this file into memory, it makes this substitution. Using the actual domain name would be less confusing for new users, but you’ll see this in most nameservers and will need to be familiar with it. You could use the full domain name in this file instead of the @ symbol if you wished, but almost nobody does that. The Data Type and Label The IN represents the type of data (x), Internet data in this case, and SOA means that this is a Start of Authority record ($). Both elements will appear in every DNS record you create. Machine Name The next part is the name of the machine where the master file lives (z). (This file was created on satariel.blackhelicopters.org.) Responsible Party Then we have the email address of the person responsible for this zone ({). Since the make-localhost script defaults to root@hostname, the email address lacks the @ sign, because the @ sign had already been assigned to mean the zone name from named.conf.[1] (Were we to put the @ in, the email address would become http://root0.0.127.in-addr.arpa.satariel.blackhelicopters.org/. That would be worse than http://root.satariel.blackhelicopters.org/, wouldn’t it?) This is important when you create your own zone files for your domains. Replace the @ in the email address with a period. In many cases, the nameserver doesn’t have a mail server on it. To follow best current practices on the Internet, replace the email address with hostmaster. and your domain name. Every domain is expected to have a “hostmaster” email address to respond to DNS issues. 283
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost PHP Web Hosting services