Resource records reference
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Resource records reference
A DNS database consists of one or more zone files used by the DNS server. Each zone holds a collection of structured resource records, the following of which are supported by the DNS Server service.
Format of DNS resource records
All resource records have a defined format that uses the same top-level fields, as described in the following table.
Field | Description |
---|---|
Owner |
Indicates the DNS domain name that owns a resource record. This name is the same as that of the console tree node where a resource record is located. |
Time to Live (TTL) |
For most resource records, this field is optional. It indicates a length of time used by other DNS servers to determine how long to cache information for a record before expiring and discarding it. For example, most resource records created by the DNS Server service inherit the minimum (default) TTL of 1 hour from the start of authority (SOA) resource record which prevents overlong caching by other DNS servers. For an individual resource record, you can specify a record-specific TTL that overrides the minimum (default) TTL inherited from the SOA RR. TTL values of zero (0) can also be used for resource records that contain volatile data not to be cached for later use after the current DNS query in progress is completed. Note
|
Class |
Contains standard mnemonic text indicating the class of the resource record. For example, a setting of "IN" indicates that the resource record belongs to the Internet class, which is the only class supported by Windows Server 2003 DNS. This field is required. |
Type |
Contains standard mnemonic text indicating the type of resource record. For example, a mnemonic of "A" indicates that the resource record stores host address information. This field is required. |
Record-specific data |
A required, variable-length field that contains information describing the resource. The format of this information varies according to the type and class of the resource record. |
A
Description: Host address (A) resource record. Maps a DNS domain name to an Internet Protocol (IP) version 4 32-bit address. For more information, see RFC 1035. |
Syntax: owner class ttl AIP_v4_address |
Example:
|
AAAA
Description: IPv6 host address (AAAA) resource record. Maps a DNS domain name to an Internet Protocol (IP) version 6 128-bit address. For more information, see RFC 1886. |
Syntax: owner class ttl AAAAIP_v6_address |
Example:
|
AFSDB
Description: Andrew File System Database (AFSDB) resource record. Maps a DNS domain name in the server_host_name field to the host name for a server computer of a server subtype. The subtype field can have either of the following recognized and supported values:
For more information, see RFC 1183. |
Syntax: owner ttl classAFSDBsubtype server_host_name |
Example:
|
ATMA
Description: Asynchronous Transfer Mode address (ATMA) resource record. Maps a DNS domain name in the owner field to an ATM address referenced in the atm_address field. Note
For more information, see "ATM Names Service" at the MFA Forum site. At the MFA Forum site, download af-saa-0069.000. |
Syntax: owner ttl class ATMAatm_address |
Example:
|
CNAME
Description: Canonical name (CNAME) resource record. Maps an aliased or alternate DNS domain name in the owner field to a canonical or primary DNS domain name specified in the canonical_name field. The canonical or primary DNS domain name used in the data is required and must resolve to a valid DNS domain name in the namespace. |
Syntax: owner ttl class CNAME canonical_name |
Example:
|
HINFO
Description: Host information (HINFO) resource record. Specifies the type of CPU and operating system in the cpu_type and os_type fields, respectively, for the host DNS domain name in the owner field. Well-known CPU and operating system types that are most often used are noted in RFC 1700. This information can be used by application protocols such as FTP, which use special procedures when communicating with computers of a known CPU and operating system type. |
Syntax: owner ttl class HINFO cpu_type os_type |
Example:
|
ISDN
Description: Integrated Services Digital Network (ISDN) resource record. Maps a DNS domain name to an ISDN telephone number. Telephone numbers used with this record should follow ITU-T E.163/E.164 international telephone numbering standards, which are compatible with current international phone numbering plans already in use. For more information, see RFC 1183. |
Syntax: owner ttl class ISDN isdn_address sub_address |
Example:
|
KEY
Description: Public key resource record. Contains a public key that is associated with a zone. In full DNSSEC implementation, resolvers and servers use KEY resource records to authenticate SIG resource records received from a signed zones. KEY resource records are signed by the parent zone, allowing a server that knows a parent zone's public key to discover and verify the child zone's key. Name servers or resolvers receiving resource records from a signed zone obtain the corresponding SIG record then retrieve the zone's KEY record. For more information, see RFC 2535. |
Syntax: owner class KEY protocol digital_signature_algorithm (DSA) public_key |
Example:
|
MB
Description: Mailbox (MB) resource record. Maps a specified domain mailbox name in the owner field to a mailbox host name in mailbox_hostname. The mailbox host name must be the same as a valid host address (A) resource record already used by a host in the same zone. Additionally, the specified host must have a domain mailbox that accepts mail for the specified owner. For more information, see RFC 1035. |
Syntax: owner ttl class MB mailbox_hostname |
Example:
|
MG
Description: Mail group (MG) resource record. Used to add domain mailboxes, each specified by a mailbox (MB) resource record in the current zone, to the domain mailing group identified by owner in this resource record. Names used in the mailbox_name field must be identical to valid mailbox (MB) resource records already present in the current zone. For more information, see RFC 1035. |
Syntax: owner ttl class MG mailbox_name |
Example:
|
MINFO
Description: Mailbox mail list information (MINFO) resource record. Specifies (in responsible_mailbox) a domain mailbox name for a responsible person who maintains a mailing list or mailbox specified in the owner field. The error_mailbox field can also be used to specify a domain mailbox that receives error messages related to this mailing list or mailbox. Mailboxes specified for responsible contacts and error forwarding must be the same as valid mailbox (MB) records that already exist in the current zone. For more information, see RFC 1035. |
Syntax: owner ttl class MINFO responsible_mailbox error_mailbox |
Example:
|
MR
Description: Mailbox renamed (MR) resource record. Specifies a domain mailbox name in new_renamed_mailbox, the proper rename of an existing mailbox specified in the owner field. An MR resource record is often used as a forwarding entry for a user who has moved to a different mailbox. MR records do not cause additional section processing. For more information, see RFC 1035. |
Syntax: owner ttl class MR new_renamed_mailbox |
Example:
|
MX
Description: Mail exchanger (MX) resource record. Provides message routing to a mail exchanger host, as specified in mail_exchanger_host, for mail sent to the domain name specified in the owner field. A 2-digit preference value indicates preferred ordering if multiple exchanger hosts are specified. Each exchanger host must have a corresponding host (A) address resource record in a valid zone. For more information, see RFC 1035. |
Syntax: owner ttl class MX preference mail_exchanger_host |
Example:
|
NS
Description: Used to map a DNS domain name as specified in owner to the name of hosts operating DNS servers specified in the name_server_domain_name field. |
Syntax: owner ttl IN NS name_server_domain_name |
Example:
|
NXT
Description: Next resource record. NXT resource records indicate the nonexistence of a name in a zone by creating a chain of all of the literal owner names in that zone. They also indicate what resource record types are present for an existing name. For more information, see RFC 2535. |
Syntax: owner class NXT next_domain_name last_record_type NXT |
Example:
|
OPT
Description: Option resource record. One OPT resource record can be added to the additional data section of either a DNS request or response. An OPT resource record belongs to a particular transport level message, such as UDP, and not to actual DNS data. Only one OPT resource record is allowed, but not required, per message. For more information, see RFC 2671. |
Syntax: nameOPT class ttl rdlen rdata |
Example:
|
PTR
Description:Pointer (PTR) resource record. Points from the name in owner to another location in the DNS namespace as specified by targeted_domain_name. Often used in special domains such as the in-addr.arpa domain tree to provide reverse lookups of address-to-name mappings. In most cases, each record provides information that points to another DNS domain name location, such as a corresponding host (A) address resource record in a forward lookup zone. For more information, see RFC 1035. |
Syntax: owner ttl class PTR targeted_domain_name |
Example:
|
RP
Description: Responsible Person (RP) resource record. Specifies the domain mailbox name for a responsible person in mailbox_name. This name is then mapped to a domain name in text_record_name for which (TXT) resource records exist in the same zone. When RP records are used in DNS queries, subsequent queries are used to retrieve associated text (TXT) resource record information. For more information, see RFC 1183. |
Syntax: owner ttl class RP mailbox_name text_record_name |
Example:
|
RT
Description: Route through (RT) resource record. Provides an intermediate host binding for internal hosts that do not have a direct wide area network (WAN) or external network connection. The RT record is similar to the MX record in that any communication from an internal host is routed through the intermediate_host for the destination DNS domain name specified in the owner field. A 2-digit preference value is used to set priority if multiple intermediate routing hosts are specified. For each intermediate host specified, a corresponding host (A) address resource record is needed in the current zone. For more information, see RFC 1183. |
Syntax: owner ttl class RT preference intermediate_host |
Example:
|
SIG
Description: Signature resource record. Encrypts a RRset to a signer's (RRset's zone owner) domain name and a validity interval. For more information, see RFC 2535. |
Syntax: owner class SIG ttl signature_expiration signature_inception key_identifier signer_name{digital_signature} |
Example:
|
SOA
Description: Start of authority (SOA) resource record. Indicates the name of origin for the zone and contains the name of the server that is the primary source for information about the zone. It also indicates other basic properties of the zone. The SOA resource record is always first in any standard zone. It indicates the DNS server that either originally created it or is now the primary server for the zone. It is also used to store other properties such as version information and timings that affect zone renewal or expiration. These properties affect how often transfers of the zone are done between servers authoritative for the zone. For more information, see Managing authority records. Note
|
Syntax: owner class SOA name_server responsible_person (serial_number refresh_interval retry_interval expiration minimum_time_to_live) |
Example:
|
SRV
Description: Service locator (SRV) resource record. Allows multiple servers providing a similar TCP/IP-based service to be located using a single DNS query operation. This record enables you to maintain a list of servers for a well-known server port and transport protocol type ordered by preference for a DNS domain name. For example, in Windows Server 2003 DNS, it provides the means to locate domain controllers that use Lightweight Directory Access Protocol (LDAP) service over TCP port 389. The purposes of each of the specialized fields used in an SRV resource record are as follows:
For more information, see the Internet draft "A DNS RR for specifying the location of services (DNS SRV)." |
Syntax: service.protocol.name ttl class SRV preference weight port target |
Example:
|
TXT
Description: Text (TXT) resource record. Maps a DNS domain name specified in the owner field to a string of characters in text_string serving as descriptive text. For more information, see RFC 1035. |
Syntax: owner ttl class TXT text_string |
Example:
|
WKS
Description: Well-known service (WKS) resource record. Describes the well-known TCP/IP services supported by a particular protocol on a specific IP address. WKS records provide TCP and UDP availability information for TCP/IP servers. If a server either supports both TCP and UDP for a well-known service or has multiple IP addresses that support a service, then multiple WKS records are used. For more information, see RFC 1035. |
Syntax: owner ttl classWKS address protocol service_list |
Example:
|
X25
Description: X.25 (X25) resource record. Maps a DNS domain name in the owner field to a Public Switched Data Network (PSDN) address number specified in psdn_number. PSDN numbers used with this record should follow the X.121 international numbering plan. For more information, see RFC 1183. |
Syntax: owner ttl classX25 psdn_number |
Example:
|