Resource records comprise the data within a DNS zone. There is no fixed limit to the number of resource records a zone can own. In general, there can be zero, one, or more resource records of a given type. However, there are constraints on the number of certain types of records a zone can have.
All resource records have these required entries:
•Name—Name (host) that owns the record, such as example.com.
•Class (not required for all formats)—DNS supports only the IN (Internet) class of record.
•TTL (time to live)—Amount of time to store the record in cache, in seconds. If you do not include a TTL, Network Registrar uses the zone default TTL, defined in the SOA resource record.
•Type—Type of the record, such as A, NS, SOA, and MX. There are many types that various RFCs define, although ten or fewer are in common use.
•Record data—Data types whose format and meaning varies with record type.
Table A-1 lists all the resource record types Network Registrar supports. It provides the field syntax and the field descriptions, as well as how the fields are represented in the Network Registrar GUI.
Table A-1 Resource Records
Syntax and Description
Host Address— Name-to-address mapping for the zone
name ttl class A address
Web UI: Add or Edit Host for Zone page: Hostname, IP Address or Resource Records for Zone page: Name, TTL, Type, Data
nrcmd> zone example.com addRR host123 3600 IN A
host123 3600 IN A 192.168.40.123
GUI: Add Resource Record A tab: Name, TTL, Class=IN, Type=A, Address
A6 (replaces AAAA records)
name ttl class A6 address
In the data, the suffix address is an IPv6 address encoded in network order (high-order octet first). There must be exactly enough octets in this field to contain a number of bits equal to 128 minus prefix length, with 0 to 7 leading pad bits to make this field an integral number of octets. Pad bits, if present, must be set to zero when loading a zone file and ignored on reception. For example:
Web UI: Resource Records for Zone page: Name, TTL, Type=A6, Data=prefixlength suffixaddr prefixname, with data in the form:
nrcmd> zone example.com addRR host456 A6 0
host456 IN A6 0 1345:c1:ca11:1234:5678:9abc:def0
GUI: Add Resource Record Generic tab: Name, TTL, Class=IN, Type=A6, Data=prefixlength suffixaddr prefixname, with data in the form:
name ttl class AAAA address
Data is the IPv6 address format of eight sets of four hexadecimal digits, separated by colons. The first set of four digits is the high-order 16 bits of the address. You can omit leading zeros in sets and omit a value in a set if the value of the set is zero.
Web UI: Resource Records for Zone page: Name, TTL, Type=AAAA, Data=address
nrcmd> zone example.com addRR host456 AAAA
You cannot have any other resource records associated with a CNAME. Aliases are useful when you want the outside world to know a single, easily remembered name. You can also use aliases when a host changes its name. In that case, ensure that you have a CNAME pointer so that when people use the original name, it can be resolved to the newer one.
Web UI: Resource Records for Zone page: Name=alias, TTL=CNAME, Type, Data=canonicalname
nrcmd> zone example.com addRR host456 CNAME
Naming Authority Pointer— Produces a new domain label or Universal Resource Identifier (URI). You can then use DNS to look up services for many resource names that are not in domain name syntax.
name ttl class NAPTR order pref flags serv regexp replace
•order—16-bit integer for the order in which to process the NAPTR records to ensure the correct ordering of rules, with low numbers processed before high numbers.
•pref—16-bit unsigned integer for the order in which to process NAPTR records with equal order values, with low numbers processed before high numbers.
•flags—Character-string containing flags to control aspects of rewriting and interpreting fields, single characters from the set [A-Z0-9] (not case-sensitive); the S, A and U flags denote a terminal lookup, the P flag says that the remainder of the application-side algorithm should be carried out protocol-specific.
•serv—Valid protocols or services.
•regexp—String containing a substitution expression applied to the original string held by the client to construct the next domain name to look up.
•replace—Next FQDN to query for NAPTR, SRV, or address records, depending on the value of the flags field.
Web UI: Resource Records for Zone page: Name, State, TTL, Type=NAPTR, Data=order pref flags service regexp replace
nrcmd> zone 8.6.4.e164.arpa addRR 188.8.131.52.6.7.9
naptr 100 10 u sip+E2U /^.*$/sip:email@example.com/ .
184.108.40.206.6.7.8 IN NAPTR 100 10 "u" "sip+E2U"
nrcmd> dns reload
GUI: Add Resource Record Generic tab: Name, TTL, Class=IN, Type=NAPTR, Data=order pref flags service regexp replace
Name Server— Authoritative server for the zone
name ttl class NS nameserver
Machines that provide name service must not reside in the owner domain. For each domain, you must have at least one NS record. NS records for a domain must exist in both the zone that delegates the domain and in the domain itself. NS record names must have an equivalent A record (they cannot point to an alias).
Web UI: Add or Edit Zone page Nameservers: NS TTL, Add Nameserver
nrcmd> zone example.com addRR @ NS
@ IN NS DNSserv2.example.com.
GUI: Add Resource Record NS tab: Name, TTL, Class=IN, Type=NS, Server
Network Service Access Point (NSAP) Address
name ttl class NASP NSAPaddr
Data is the NSAPaddr—Octet values assigned by the assigning authority, a character string of the type used in TXT and HINFO records (see RFC 1706).
Web UI: Resource Records for Zone page: Name, TTL, Type=NSAP, Data=NSAPaddr
nrcmd> zone example.com addRR host10 NSAP
host10 IN NSAP
Data is the domain name of host having the reverse record indicated by the owner. PTR records are used for reverse mapping, specifically in the in-addr.arpa zones for translation of addresses to names. PTRs use official names, not aliases. The name in a PTR record is the local IP address portion of the reverse name.
Web UI: Resource Records for Zone page: Name, State, TTL, Type=PTR, Data=dname
nrcmd> zone example.com addRR
220.127.116.11.in-addr.arpa. PTR host1234
18.104.22.168.in-addr.arpa. IN PTR
Start of Authority— Every zone must have a single SOA record
name ttl class SOA primeserver hostmaster(serial refresh retry expire minimum)
Web UI: Add or Edit Zone page SOA Attributes: Serial Number, SOA TTL, Nameserver, Contact E-Mail, Secondary Refresh, Secondary Retry, Secondary Expire, Minimum TTL
nrcmd> zone example.com addRR @ 172800 IN SOA ns
hostmaster 1 10800 3600 604800 86400
@ IN SOA ns.example.com. hostmaster.example.com. 1
10800 3600 604800 86400
nrcmd> dns reload
GUI: Primary Zone SOA tab: Name, TTL, Contact e-mail address, Name of primary server, Serial number, Secondary refresh time, Secondary retry time, Secondary expire time, Minimum TTL
name ttl class SRV priority weight port target
•priority—16-bit priority to give the record among the owner SRV records.
•weight—16-bit load to give the record at the same priority level.
•port—16-bit port on which to run the service.
•target—Domain name of host running on the specified port.
Administrators can use several servers for a single domain, move services between hosts with little difficulty, and designate some hosts as primary servers for a service and others as backups. Clients ask for a specific service or protocol for a domain and receive the names of any available servers. See "Windows 2000 Interoperability," for how this record affects Windows 2000 servers.
Web UI: Resource Records for Zone page: Name, TTL, Type=SRV, Data=priority weight port target
nrcmd> zone example.com addRR host2 SRV 10 1 60
host2 IN SRV 10 1 60 host7.example.com.
GUI: Add Resource Record Generic tab: Name, TTL, Class=IN, Type=SRV, Data=priority weight port target
name ttl class TXT textstring
Data is one or more text character strings that can contain any type of information.
Web UI: Resource Records for Zone page: Name, TTL, Type=TXT, Data=textstring
nrcmd> zone example.com addRR host2 TXT "this