Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Get The TCP/IP Guide for your own computer.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  Name Systems and TCP/IP Name Registration and Name Resolution
           9  TCP/IP Name Systems: Host Tables and Domain Name System (DNS)
                9  TCP/IP Domain Name System (DNS)
                     9  DNS Name Servers and Name Resolution
                          9  DNS Messaging and Message, Resource Record and Master File Formats

Previous Topic/Section
DNS Name Notation and Message Compression Technique
Previous Page
Pages in Current Topic/Section
12
3
4
Next Page
DNS Changes To Support IP Version 6
Next Topic/Section

DNS Master File Format
(Page 3 of 4)

Master File Directives

In addition to resource records, most master file implementations also support the use of directives. These are commands that specify certain important pieces of information to guide how the master file is to be interpreted. Three of the most common directives are:

  • $ORIGIN: Specifies the domain name that is appended to unqualified specifications; this is the “base” used to convert PQDNs to FQDNs. For example, if the origin is “xyzindustries.com.”, then a PQDN such as “sales” will be interpreted as “sales.xyzindustries.com.”. Once defined, the origin can be referenced by just using “@” in place of a name, as we will see in the example at the end of this topic.

  • $TTL: Specifies the default Time To Live value to be used for any resource records that do not specify a TTL value in the record itself. (This value was formerly specified by the Minimum field in the Start Of Authority record.)

  • $INCLUDE: Allows one master file to include the contents of another. This is sometimes used to save the duplication of certain entries that are common between zones.
Syntax Rules for Master Files

There are a few other syntax rules for DNS master files, some of which are intended to save further time or energy on the part of administrators:

  • Multiple-Record Shorthand: If multiple consecutive records pertain to the same domain, the “<domain-name>” is specified for the first one, and can be then be left blank for the subsequent ones. The server will assume that any resource records without a “<domain-name>” indicated apply to the last “<domain-name>” it saw.

  • Comments: A semicolon (“;”) marks a comment. Any text from the semicolon until the end of the line is ignored.

  • Escape Character: A backslash (“\”) is used to “escape” the special meaning of a character. For example, a double-quote (") is used to delimit text strings; a literal double-quote character is indicated by a backslash-double-quote combination (\").

  • White Space: Tabs and spaces are used as delimiters and blank lines are ignored. For readability, most smart administrators indent using tabs to make more clear which records belong with which names, and group records using blank lines and comments.

  • Case: Like DNS domain names, master file entries are case-insensitive.

Previous Topic/Section
DNS Name Notation and Message Compression Technique
Previous Page
Pages in Current Topic/Section
12
3
4
Next Page
DNS Changes To Support IP Version 6
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.