Page tree
Skip to end of metadata
Go to start of metadata

A
AAAA
AFSDB
CAA
CERT
CDNSKEY
CDS
CNAME
DNAME
DS
HINFO
KEY
LOC
MX
NAPTR
NS
OPENPGPKEY
PTR
RP
SOA
SPF
SSHFP
SRV
TLSA
TXT
URI



A - The A record contains an IP address. It is stored as a decimal dotted quad string

Expected format:

1.2.3.4


AAAA - The AAAA record contains an IPv6 address.

Expected format:

2001:DB8:2000:bf0::1


AFSDB - A specialised record type for the 'Andrew Filesystem'. Stored as: '#subtype hostname', where subtype is a number.


CAA - The "Certification Authority Authorization" record, specified in RFC 6844, is used to specify Certificate Authorities that may issue certificates for a domain. 

Please see https://sslmate.com/caa/ for assistance on generating this record.

Expected format:

0 issue "letsencrypt.org"


CERT - Specialised record type for storing certificates, defined in RFC 2538.


CDNSKEY - https://tools.ietf.org/html/rfc7344#section-3.2


CDS - https://tools.ietf.org/html/rfc7344#section-3.1


CNAME - The CNAME record specifies the canonical name of a record. The value must end with a period "."

Expected format:

cname.example.org.


DNAME - The DNAME record, as specified in RFC 6672 is supported. Please note, this is only supported if DNSSEC is not enabled for the parent zone. 


DS - The DS DNSSEC record type is fully supported, as described in RFC 4034.


HINFO - Hardware Info record, used to specify CPU and operating system. Stored with a single space separating these two, example: 'i386 Linux'.


KEY - The KEY record is fully supported. For its syntax, see RFC 2535.


LOC - 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


MX - The MX record specifies a mail exchanger host for a domain.

A special window will display to ensure this record is formatted correctly. 


NAPTR - https://tools.ietf.org/html/rfc2915


NS - Nameserver record. Useful if you have sub-zones delegated to other DNS providers.


OPENPGPKEY - The OPENPGPKEY records, specified in RFC TBD, are used to bind OpenPGP certificates to email addresses. (https://tools.ietf.org/html/draft-ietf-dane-openpgpkey-06)


PTR - Reverse pointer, used to specify the host name belonging to an IP or IPv6 address.


RP - Responsible Person record, as described in RFC 1183. Stored with a single space between the mailbox name and the more-information pointer. (https://tools.ietf.org/html/rfc1183)


SOA - 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.

A special window will display to ensure this record is formatted correctly. 


SPF - SPF records can be used to store Sender Policy Framework details (RFC 4408).


SSHFP - The SSHFP record type, used for storing Secure Shell (SSH) fingerprints, is fully supported. A sample from RFC 4255 is:2 1 123456789abcdef67890123456789abcdef67890.


SRV - SRV records can be used to encode the location and port of services on a domain name.


TLSA - The TLSA records, specified in RFC 6698, are used to bind SSL/TLS certificate to named hosts and ports.


TXT - The TXT field can be used to attach textual data to a domain. Text is stored plainly, PowerDNS understands content not enclosed in quotes. However, all quotes characters (") in the TXT content must be preceded with a backslash (\).

Expected format:

"This is a sample TXT record"
 - This will serve the record: This is a sample TXT record

OR

"This is a sample \"TXT\" record"
 - This will serve the record: This is a sample "TXT" record


URI - The URI record, specified in RFC 7553, is used to publish mappings from hostnames to URIs.

  • No labels