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!

Searchable, convenient, complete TCP/IP information.
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
1
2
34
Next Page
DNS Changes To Support IP Version 6
Next Topic/Section

DNS Master File Format
(Page 2 of 4)

DNS Common Master File Record Format

Just as all resource records are stored internally using a common field format, they also use a common master file format. Each record normally appears on a separate line of the file. This format is as follows, with optional fields shown in square brackets:

<domain-name>  [<ttl>]  <class>  <type>  <rdata>

The fields are as follows:

  • <domain-name>: A DNS domain name, which may be either a fully-qualified domain name (FQDN) or a partially-qualified name (PQDN). See below.

  • <ttl>: A Time To Live value, in seconds, for the record. If omitted, the default TTL value for the zone is used. In fact, most resource records do not have a specified TTL, just using the default provided by the Start Of Authority record.

  • <class>: The resource record class. For modern DNS this field is optional, and defaults to “IN” for “Internet”

  • <type>: The resource record type, specified using a text code such as “A” or “NS”, not the numeric code.

  • <rdata>: Resource record data, which is a set of space-separated entries that depends on the record type.

The “<rdata>” can be either a single piece of information or a set of entries, depending on the record type. In the case of longer record types, especially the Start Of Authority record, multiple entry “<rdata>” fields are spread over several lines and enclosed in parentheses; the parentheses make all the entries act as if they were on a single line. Note that if the “<ttl>” field is present, the order of it and the “<class>” field may be switched; this causes no problems because one is a number and the other text (“IN”).

Use and Interpretation of Partially-Qualified Domain Names

Domain names may be mixed between FQDNs and PQDNs. Partially-qualified names are used to make master files faster to create and more readable, by cutting down on the common parts of names; they are sort of the “human equivalent” of DNS message compression. A FQDN is shown as a full domain name ending in a dot (“.”) to represent the DNS name tree root. A PQDN is given as just a partial name with no root, and is interpreted as a FQDN by the software reading the master file (see the $ORIGIN directive below for more.)

It is important to remember the trailing dot to mark FQDNs; if the origin is “xyzindustries.com” and in its zone file the name “bigisp.net” appears, the server will read this as “bigisp.net.xyzindustries.com”—probably not what you want. Also, e-mail addresses, such as the <r-name> field in the SOA record, have the “@” of the e-mail address converted to a dot, following the standard DNS convention.


Previous Topic/Section
DNS Name Notation and Message Compression Technique
Previous Page
Pages in Current Topic/Section
1
2
34
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.