Choose below which record you want to understand, configure or check.
Because of caching, a DNS change may not be visible everywhere immediately. Do not delete existing email or verification records before checking what they are used for.
An A record links a host name to an IPv4 address.
Read moreAn AAAA record links a host name to an IPv6 address.
Read moreA CNAME record points one host name to another host name.
Read moreAn MX record determines which mail server receives email for your domain.
Read moreA TXT record stores text information in DNS.
Read moreSPF identifies which servers may send email on behalf of your domain.
Read moreDKIM publishes the key used to verify email signatures.
Read moreDMARC determines how recipients handle failed SPF and DKIM checks.
Read moreNS records identify the name servers that are authoritative for a DNS zone.
Read moreA CAA record determines which certificate authorities may issue SSL certificates.
Read moreAn SRV record describes the location, port and priority of a network service.
Read moreA PTR record maps an IP address back to a host name.
Read moreLearn how to configure an A record to point a website or subdomain to an IPv4 address.
Read moreLearn how to configure an AAAA record to point a website or subdomain to an IPv6 address.
Read moreLearn how to configure a CNAME record as an alias to another host name.
Read moreLearn how to configure an MX record to direct incoming email to a mail server.
Read moreLearn how to configure a TXT record for verification or policy information.
Read moreLearn how to configure a TXT record with authorised sending servers.
Read moreLearn how to configure a TXT record for email signature verification.
Read moreLearn how to configure a TXT record for email authentication reporting and policy.
Read moreLearn how to configure a CAA record to restrict which certificate authority may issue certificates.
Read moreLearn how to configure an SRV record to publish a network service.
Read moreLearn how to configure an A or CNAME record to catch all non-existent subdomains.
Read moreLearn how to configure an A or AAAA record to point a subdomain to another server.
Read moreResolvers temporarily retain DNS responses according to the TTL. As a result, a change may not be visible everywhere immediately.
Read moreAn old DNS cache, local hosts file or proxy may still point to the previous address.
Read moreIncorrect or duplicate MX, SPF, DKIM or DMARC records can cause email problems.
Read moreCheck that exactly one SPF policy exists and that it includes all legitimate sending servers.
Read moreCheck the selector, host name and public key when DKIM validation fails.
Read moreCheck that the record is located at _dmarc and contains a valid DMARC version and policy.
Read more
