3.3 Supported RR types
The `type' column in the `rr' table may contain any of the following
supported resource record types:
- A host address. The `data' column should contain the IP address (in
numbers-and-dots format) associated with the `name'.
- An IPv6 host address. The `data' column should contain the IPv6 address
associated with the `name'.
- A server side alias. An alias is like a
CNAME, only it is handled entirely
by the server. The `data' column should contain the hostname aliased
by `name'. Aliases can be used in place of
A records. The client will
A records and will not be able to tell that aliases are involved.
The hostname specified by `data' must exist in the database.
It can be useful to use aliases for everything. Use
A records for the
canonical name of the machine and use aliases for any additional names.
This is especially useful when combined with automatic
PTR records. If a
single IP address is only used for one
A record, then there will never be
any confusion over what the
PTR record should be.
In order for server-side aliases to work, MyDNS must have been compiled with
example: `albuquerque.example.com.' (FQDN)
example: `albuquerque' (hostname only)
- The canonical name for an alias. The `data' column should contain the real name
of the machine specified by `name'. `data' may be a hostname or an FQDN.
example: `porcini.example.com.' (FQDN)
example: `porcini' (hostname only)
- Host information. The `data' column should contain two strings which provide information
about the host specified by `name'. The first string specifies the CPU type, and the
second string describes the operating system type. The two strings should be separated by
a space. If either string needs to contain a space, enclose it in quotation marks.
example: `"Pentium Pro" Linux'
- Mail exchange. The `data' column should contain the hostname or FQDN of a mail server
which will accept mail for the host specified by `name'. The `aux' column should
contain a preference for this mail server. Mail transfer agents prefer MX records with
lower values in `aux'.
example: `ns0.example.com.' (FQDN)
example: `ns0' (hostname only)
- An authoritative nameserver. The `data' column should contain the hostname or FQDN of a
server which should be considered authoritative for the zone listed in `name'.
example: `france.example.com.' (FQDN)
example: `france' (hostname only)
- A domain name pointer. These records, used only with IN-ADDR.ARPA zones, should contain the
canonical hostname of the machine referred to by `name' in `data'.
- A responsible person. The `data' column should contain the DNS-encoded email address of
the person responsible for the name requested, then a space, then a hostname
that should return a TXT record containing additional information about the responsible
person. If there is no such TXT record, the second value should contain a dot (`.').
example: `webmaster.example.com. contactinfo.example.com.'
- Server location. Specifies the location of the server(s) for a specific protocol and domain. The `data'
column must contain three space-separated values. The first value is a number specifying the weight for
this entry. The second field is a number specifying the port on the target host of this service. The
last field is a name specifying the target host. The `aux' column should contain the priority of
this target host. Targets with a lower priority are preferred.
For more information, read RFC 2782.
example: `0 9 server.example.com.' (FQDN)
example: `0 9 server' (hostname only)
- A text string. The `data' column contains a text string that is returned only when a TXT query
is issued for the host specified by `name'.
example: `This is a string.'