<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 22. Supported record types and their storage</title><link rel="stylesheet" href="docbook.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="index.html" title="PowerDNS manual" /><link rel="up" href="index.html" title="PowerDNS manual" /><link rel="prev" href="metrics.html" title="Chapter 21. Index of all Authoritative Server metrics" /><link rel="next" href="faq.html" title="Chapter 23. HOWTO & Frequently Asked Questions" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 22. Supported record types and their storage</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="metrics.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="faq.html">Next</a></td></tr></table><hr /></div><div class="chapter" title="Chapter 22. Supported record types and their storage"><div class="titlepage"><div><div><h2 class="title"><a id="types"></a>Chapter 22. Supported record types and their storage</h2></div></div></div><p>
This chapter lists all record types PDNS supports, and how they are stored in backends. The list is mostly alphabetical but
some types are grouped.
</p><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="warning.png" /></td><th align="left">Warning</th></tr><tr><td align="left" valign="top"><p>Host names and the MNAME of a SOA records are NEVER terminated with a '.' in PowerDNS storage! If a trailing '.' is present
it will inevitably cause problems, problems that may be hard to debug.</p></td></tr></table></div><p>
The PowerDNS Recursor can serve and store all record types, regardless of whether these are explicitly supported.
</p><div class="variablelist"><dl><dt><span class="term">A</span></dt><dd><p>
The A record contains an IP address. It is stored as a decimal dotted quad string,
for example: '213.244.168.210'.
</p></dd><dt><span class="term">AAAA</span></dt><dd><p>
The AAAA record contains an IPv6 address. An example: '3ffe:8114:2000:bf0::1'.
</p></dd><dt><span class="term">AFSDB (since 2.9.21)</span></dt><dd><p>
Specialised record type for the 'Andrew Filesystem'. Stored as: '#subtype hostname', where subtype is a number.
</p></dd><dt><span class="term">CERT (since 2.9.21)</span></dt><dd><p>
Specialised record type for storing certificates, defined in RFC 2538.
</p></dd><dt><span class="term">CNAME</span></dt><dd><p>
The CNAME record specifies the canonical name of a record. It is stored plainly. Like all other records, it is not
terminated by a dot. A sample might be 'webserver-01.yourcompany.com'.
</p></dd><dt><span class="term">DNSKEY (since 2.9.21)</span></dt><dd><p>
The DNSKEY DNSSEC record type is fully supported, as described in RFC 3757. Before 3.0 PowerDNS didn't do any DNSSEC prcessing, since 3.0 PowerDNS
is able to fully process DNSSEC. This can be done with <a class="link" href="pdnssec.html" title="5. 'pdnssec' for PowerDNSSEC command & control">pdnssec</a>.
</p></dd><dt><span class="term">DS (since 2.9.21)</span></dt><dd><p>
The DS DNSSEC record type is fully supported, as described in RFC 3757. Before 3.0 PowerDNS didn't do any DNSSEC prcessing, since 3.0 PowerDNS
is able to fully process DNSSEC. This can be done with <a class="link" href="pdnssec.html" title="5. 'pdnssec' for PowerDNSSEC command & control">pdnssec</a>.
</p></dd><dt><span class="term">HINFO</span></dt><dd><p>
Hardware Info record, used to specify CPU and operating system. Stored with a single space separating these two,
example: 'i386 Linux'.
</p></dd><dt><span class="term">KEY (since 2.9.21)</span></dt><dd><p>
The KEY record is fully supported. For its syntax, see RFC 2535.
</p></dd><dt><span class="term">LOC</span></dt><dd><p>
The LOC record is fully supported. For its syntax, see RFC 1876. A sample content would be: '51 56 0.123 N 5 54 0.000 E 4.00m 1.00m 10000.00m 10.00m'
</p></dd><dt><span class="term">MX</span></dt><dd><p>
The MX record specifies a mail exchanger host for a domain. Each mail exchanger also has a priority or preference.
This should be specified in the separate field dedicated for that purpose, often called 'prio'.
</p></dd><dt><span class="term"><a id="naptr"></a>NAPTR</span></dt><dd><p>
Naming Authority Pointer, RFC 2915. Stored as follows:
</p><pre class="screen">
'100 50 "s" "z3950+I2L+I2C" "" _z3950._tcp.gatech.edu'.
</pre><p>
The fields are: order, preference, flags, service, regex,
replacement. Note that the replacement is not enclosed in quotes, and should not be. The replacement may be omitted, in which
case it is empty. See also RFC 2916 for how to use NAPTR for ENUM (E.164) purposes.
</p></dd><dt><span class="term">NS</span></dt><dd><p>
Nameserver record. Specifies nameservers for a domain. Stored plainly: 'ns1.powerdns.com', as always without a terminating dot.
</p></dd><dt><span class="term">NSEC (since 2.9.21)</span></dt><dd><p>
The NSEC DNSSEC record type is fully supported, as described in RFC 3757. Before 3.0 PowerDNS didn't do any DNSSEC prcessing, since 3.0 PowerDNS
is able to fully process DNSSEC. This can be done with <a class="link" href="pdnssec.html" title="5. 'pdnssec' for PowerDNSSEC command & control">pdnssec</a>.
</p></dd><dt><span class="term">PTR</span></dt><dd><p>
Reverse pointer, used to specify the host name belonging to an IP or IPv6 address. Name is stored plainly: 'www.powerdns.com'.
As always, no terminating dot.
</p></dd><dt><span class="term">RP</span></dt><dd><p>
Responsible Person record, as described in RFC 1183. Stored with a single space between the mailbox name and the more-information
pointer. Example 'peter.powerdns.com peter.people.powerdns.com', to indicate that peter@powerdns.com is responsible and that more
information about peter is available by querying the TXT record of peter.people.powerdns.com.
</p></dd><dt><span class="term">RRSIG (since 2.9.21)</span></dt><dd><p>
The RRSIG DNSSEC record type is fully supported, as described in RFC 3757. Before 3.0 PowerDNS didn't do any DNSSEC prcessing, since 3.0 PowerDNS
is able to fully process DNSSEC. This can be done with <a class="link" href="pdnssec.html" title="5. 'pdnssec' for PowerDNSSEC command & control">pdnssec</a>.
</p></dd><dt><span class="term"><a id="soa-type"></a>SOA</span></dt><dd><p>
The Start of Authority record is one of the most complex available. It specifies a lot about a domain: the name
of the master nameserver ('the primary'), the hostmaster and a set of numbers indicating how the data in this domain
expires and how often it needs to be checked. Further more, it contains a serial number which should rise on each change
of the domain.
</p><p>
The stored format is:
</p><pre class="screen">
primary hostmaster serial refresh retry expire default_ttl
</pre><p>
Besides the primary and the hostmaster, all fields are numerical. PDNS has a set of default values:
</p><div class="table"><a id="idp8979808"></a><p class="title"><b>Table 22.1. SOA fields</b></p><div class="table-contents"><table summary="SOA fields" border="1"><colgroup><col /><col /></colgroup><tbody><tr><td>primary</td><td><span class="command"><strong>default-soa-name</strong></span> configuration option</td></tr><tr><td>hostmaster</td><td>hostmaster@domain-name</td></tr><tr><td>serial</td><td>0</td></tr><tr><td>refresh</td><td>10800 (3 hours)</td></tr><tr><td>retry</td><td>3600 (1 hour)</td></tr><tr><td>expire</td><td>604800 (1 week)</td></tr><tr><td>default_ttl</td><td>3600 (1 hour)</td></tr></tbody></table></div></div><p><br class="table-break" />
</p><p>
The fields have complicated and sometimes controversial meanings. The 'serial' field is special. If left at 0, the default,
PDNS will perform an internal list of the domain to determine highest change_date field of all records within the zone, and use
that as the zone serial number. This means that the serial number is always raised when changes are made to the zone, as long
as the change_date field is being set. Make sure to check whether your backend of choice supports Autoserial.
</p></dd><dt><span class="term">SPF (since 2.9.21)</span></dt><dd><p>
SPF records can be used to store Sender Policy Framework details (RFC 4408).
</p></dd><dt><span class="term">SSHFP (since 2.9.21)</span></dt><dd><p>
The SSHFP record type, used for storing Secure Shell (SSH) fingerprints, is fully supported. A sample from RFC 4255 is:
'2 1 123456789abcdef67890123456789abcdef67890'.
</p></dd><dt><span class="term">SRV</span></dt><dd><p>
SRV records can be used to encode the location and port of services on a domain name. When encoding, the priority field
is used to encode the priority. For example, '_ldap._tcp.dc._msdcs.conaxis.ch SRV 0 100 389 mars.conaxis.ch' would be
encoded with 0 in the priority field and '100 389 mars.conaxis.ch' in the content field.
</p></dd><dt><span class="term">TXT</span></dt><dd><p>
The TXT field can be used to attach textual data to a domain. Text is stored plainly.
</p></dd></dl></div><p>
</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="metrics.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="faq.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 21. Index of all Authoritative Server metrics </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 23. HOWTO & Frequently Asked Questions</td></tr></table></div></body></html>
