DNS/DHCP Management Console
A Resource Record (RR) contains data associated with domain names. This data is represented by and is subordinate to the Resource Record Set (RR Set) of a zone container.
You can create the following types of Resource Records.
A6 records can specify a complete IPv6 address or only a part of it, such as
the last 64 bits assigned to a host's network interface, and then refer to the
remainder
of the address by a symbolic domain name. The part of the address specified
in this record is called Address Suffix.
This record has prefix information required to build the complete IPv6 address. Prefix information comprises a prefix length and a DNS name which is in turn the owner of one or more A6 records.
If you select this option, you must specify the following:
Prefix Length: A decimal value between 0 and 128, inclusive. This is the number of bits of the prefix that is not specified in this A6 record.
Address Suffix: An IPv6 address. This need not be specified if the prefix length is 128.
Prefix Name: The domain name that has the prefix part of the IPv6 address. This need not be specified if the prefix length is 0.
For more details about A6 record, see RFC 2874.
Maps a domain name to an IPv4 address. To create an A record, you must specify the IPv4 address that is associated with the domain name.
For more details about A record, see RFC 1035.
Maps a domain name to an IPv6 address . To create an AAAA record , you must specify the IPv6 address that is associated with the domain name.
For more details about AAAA record, see RFC1886.
The AFS system uses the DNS to map from a domain name to the name of an AFS cell database server or Open Group's Distributed Computing Environment (DCE) cell's authenticated name server. It contains the following data:
Subtype: An integer specifying the type of server this record
is pointing to. Value 1 indicates AFS cell database server and value 2 indicates
DCE cell's authenticated name server.
Hostname: The domain name of the host on which the server pointed by this record is running.
For more details about AFSDB record, see RFC1183.
Specifies the canonical or primary name for the owner. The owner name is the
alias name given to the primary name.
To create a CNAME record, enter the alias in the owner name field and the primary
name in the domain name of the aliased host field.
A DNAME-record is used to map or rename an entire sub-tree of the DNS name space to another domain. It differs from the CNAME-record which maps only a single node (leaf or terminal node) of the name space. DNAME resource record is useful when an organization renaming or network renumbering occurs. The transition can be done easily using DNAME resource records.
To create a DNAME record, specify the domain name to be renamed in the owner
name field and the domain name to which it is to be renamed in the target domain
name field.
For more details about DNAME record, see RFC 2672.
A HINFO-record maps a host domain name to its CPU and operating system type.
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. HINFO record has the following RDATA fields:
CPU: A character string which specifies the CPU type
OS: A character string which specifies the operating system type
Standard CPU types can be found at http://www.iana.org/assignments/machine-names
Standard operating system types can be found at http://www.iana.org/assignments/operating-system-names
For more details about HINFO record, see RFC1035.
Integrated Service Digital Network (ISDN) resource record maps a domain name
to an ISDN telephone number.
To create an ISDN record, enter the following fields:
ISDN Address: ISDN Address format is generally a string of decimal digits containing the country code, area code, etc. The ISDN phone numbers used should follow the ITU-T E.163/E.164 international telephone numbering standards.
Sub Address: The format of subaddress is normally a string of hexadecimal digits. This is an optional field.
This resource record provides capability to specify the location information of computers, subnets, and networks in the globe. This record has the following fields:
The valid range for degrees is 0 to 90, minutes is 0 to 59, and seconds is 0 to 59.999. The seconds and minutes field are optional. If a value has not been specified for these fields, the default value 0 will be configured.
The valid range for degrees is 0 to 180, minutes is 0 to 59, and seconds is 0 to 59.999. The seconds and minutes field are optional. If a value has not been specified for these fields, the default value 0 will be configured.
The valid range is -100000.00 to 42849672.95. A maximum of two digits can be specified after the decimal point.
The valid range is 0 to 90000000.00. This is an optional field. The default value is 1m. A maximum of two digits can be specified after the decimal point.
The valid range is 0 to 90000000.00. This is an optional field. The default value is 10000m. A maximum of two digits can be specified after the decimal point.
The valid range is 0 to 90000000.00. This is an optional field. The default value is 10m. A maximum of two digits can be specified after the decimal point.
For more details about LOC record, see RFC 1876.
To get the latitude and longitude information of a particular location, visit
http://www.ckdhr.com/dns-loc/finding.html
For useful links and utilities to create LOC records, visit http://www.ckdhr.com/dns-loc
Lists the machine where a user wants to receive mails.
To create an MB record, specify the user's login name in the owner name field,
and the domain name of the mailbox address and the domain name of the machine
to which mails for this user will be delivered in the mailbox address domain
name field.
For more details about MB record, see RFC 1035.
Specifies the mail group members (one MG-record per member).
To create an MG record, specify the mail group name in the owner name field,
and email address of the mail group member (with the '@' symbol replaced by
'.') in the mail group member domain name.
MINFO record is generally used to create a mail group for a mailing list.
To create an MINFO record, enter the name of the mail group in the owner name
field. This record has the following fields:
Responsible MailBox: Enter the mailbox name of the person responsible for maintaining this list. Requests mails to add to this mail group will be sent to this mail box.
Error Message MailBox: Enter the mailbox name to which the error messages related to the mailing list should be delivered.
A domain name that specifies the mailbox that is the proper rename of the specified mailbox.
MX records identifies mail servers responsible for a domain name.
To create an MX record, enter the domain name to which you want to create an
MX record in the owner name field. You must specify the following fields:
Preference: An integer between 0 and 65,535 that specifies the preference given to this resource record among other MX records created for the same owner. Lower values for this field gives more preference to this record.
Exchange: A domain name that specifies a host willing to act as a mail server for the owner name.
For more information about MX record, see RFC 1035.
NS-records identify the DNS servers responsible (authoritative) for a zone.
A zone should contain one NS-record for each DNS servers (primary and secondary)
managing this zone. This record is used for zone transfer purposes (notify)
and in domain delegation.
To create an NS record, enter the domain name in the owner name field and the
domain name of the server in the DNS Server domain name field.
For more details about NS record see RFC1035.
Generally PTR record is used to map a host's IP address to its domain name. Its functionality is
the reverse of an A record. A PTR record can also be used to point a
domain name to another domain name. The later usage of PTR record is generally
required for achieving classless in-addr.arpa delegation.
To create a PTR record for mapping a host IP address to its domain
name, enter the host id part of IP address in reverse order in the
editable part of owner name field. Fill host name and domain name fields
with the corresponding values form domain name of the host.
To create a PTR record for mapping one domain name to another domain name, enter the domain name which points to another domain name in owner name field (you may need to enter only part of it as zone name part of it is already filled in). Fill host name and domain name fields with the corresponding values from domain name pointed by owner name.
For more details about PTR record, see RFC1035.
Contains X.400 mail mapping information with the following parameters:
Preference: A 16-bit integer that specifies the preference given to this resource record among others at the same owner.
MAP822: A domain name element containing the RFC822 part of the MCGAM.
MAPX400: A domain name element containing the value derived from the X.400 part of the MCGAM.
For more details about PX record, see RFC2163.
Specifies the mailbox of the person responsible for the host or domain name. The SOA record of a zone defines the person responsible for the entire zone, but a zone might contain a large number of individual hosts or domain names for which different people are assigned responsibility. The RP-record type makes it possible to identify the responsible person for individual domain names contained within the zone.
To create an RP record, enter the host or domain name to which you want to assign a responsible person in the owner name field.
RP record has the following fields:
Responsible Person's Mailbox: A domain name that specifies the mailbox for the responsible person. The root domain name (just ".") can be specified to indicate that there is no mailbox available for this person.
TXT-RR Domain Name : A domain name of TXT record which contains the details about the responsible person. The root domain name (just ".") can be specified to indicate that no TXT record exists.
For more details about RP record, see RFC1183.
Specifies an intermediate host that provides routing to the domain name (host) of the record. This can be used by computers which are not directly connected to the Internet or wide area network WAN).
Preference: An integer value representing the preference of the route among other RT records for the same domain name. Lower values for this fields gives more preference to this record.
Intermediate: The domain name of a host that will serve as an intermediate in reaching the host specified by the owner name of this record.
Specifies the location of services with the following parameters:
Service: The symbolic name of the desired service.
Proto: The protocol on which the above service is available.
Priority: The priority assigned to the target host. A client attempts to contact the target host with the lowest-numbered preference.
Weight: This value is used for load balancing. When a client has to choose a target among the hosts that have the same priority, the probability of selecting a particular host depends upon the weight value assigned to it.
Port: The port on which this service is available using the protocol specified in the Proto field.
Target: The domain name of the host on which this service is available. This domain name should have an A record associated with it..
For more details about SRV record, see RFC 2782.
TXT-records are used to hold descriptive text that contains general information about a domain name such as who is hosting it, contact person, phone numbers, etc. These records are informational for people and are not required for any DNS functions. The RDATA field for this record can be used to enter descriptive text.
For more details about TXT record, see RFC1035.
Specifies the well-known services available on a host using a given protocol. This record has three RDATA fields: IP Address, protocol, and available services. IP address and protocol specifies the address and protocol on which one or more services are available. Available services lists all the services available on a host using the above IP address and protocol.
For more details about X25 record, see RFC 1183.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For more information, see Legal Notices.