RRPproxy Homepage
RRPproxy Homepage

Resource records

A

32-bit IPv4 address, used to map hostnames to an IP address of the host.

  • test.example.com. 28800 IN A 192.0.2.1

AAAA

128-bit IPv6 address, used to map hostnames to an IP address of the host.

  • test.example.com. 28800 IN AAAA 2001:0db8:85a3:0000:0000:8a2e:0370:7334

CAA

Specifies which certificate authorities are allowed to issue a SSL certificate for a domain.

  • test.example.com. IN CAA 0 issue digicert.com

CNAME

Alias of the domain name, the DNS lookup will continue by retrying the lookup with the new name.

  • foo.example.com. 28800 IN CNAME bar.example.com.

MX

Mail exchange record, maps a domain name to a mailserver for that domain. Composed of priority, a 16 bit integer, and the hostname of the mailserver.

  • example.com. 28800 IN MX 10 mail.example.com.

NAPTR

Naming Authority Pointer, allows regular expression based rewriting of domain names which can then be used as URIs, further domain names to lookups, etc. NAPTR records are composed of a priority, a preference, which helps to order records with identical priority, similar to the SRV records weight, a flag for the returned record type, a service name, which is offered by the server, a regular expression rule and a replacement.

  • srv.ex.com. 28800 IN NAPTR 100 10 "A" "" "!^.*$!prodsrv.ex.com!"

NS

Delegates a DNS zone to use the given authoritative name servers.

  • ns1.example.com. 28800 NS nameserver.example.org.

SRV

Service location record, used for newer protocols instead of creating protocol-specific records such as MX. The SRV record is composed of a priority, a weight, which serves as second level priority between services with identical priority, a port, the TCP or UDP port where the service can be found, and the target, the name of the service providing host.

  • _jabber._tcp.example.com. 28800 IN SRV 0 5 5060 jabber.example.com

TXT

Free definable, descriptive text.

  • test.example.com. 28800 IN TXT "Free T-Shirts for all!"

X-HTTP

X-HTTP records are pseudo resource records in our system representing webforwardings. The resource data is composed of redirection type (REDIRECT or FRAME) and the target. Note that pseudo records will neither appear in the records list nor in the exported BIND file. The creation of a X-HTTP pseudo record will also add an A record though, which can not be deleted as long as the forwarding exists.

  • forwarding.example.org. 28800 IN X-HTTP REDIRECT http://target.example.com

X-SMTP

X-SMTP records are pseudo resource records in our system representing mailforwardings. Note that pseudo records will neither appear in the records list nor in the exported BIND file. The first creation of a X-SMTP pseudo record will also add a MX record though, which can not be deleted as long as any mailforwarding exists.

The example shows a forwarding from 'itsame@mario.example.org' to 'mariobros@example.com'.

  • mario.example.org. 28800 IN X-SMTP itsame@ MAILFORWARD mariobros@example.com

Wedomains :)