Our Windows and Linux hosting systems support the following DNS record types: A, AAAA, CAA, CNAME, MX, SRV, and TXT. These records handle the core functions required by most domains, from resolving hostnames to IP addresses and routing email to enforcing security policies.

Correct DNS configuration directly affects site availability, email deliverability, and security. Misconfigured records can cause outages, failed authentication, or certificate issuance problems. The types listed above address the needs of the vast majority of web, mail, and application hosting scenarios without requiring esoteric record types.

#Supported DNS Record Types

Each record type serves a distinct purpose. Below are detailed explanations of their functions and typical use cases.

  • A: Maps a domain name or subdomain to a 32-bit IPv4 address. This is the fundamental record that tells browsers and clients where to find your web server. Without a valid A record, visitors cannot reach your site via the domain.
  • AAAA: Maps a domain name to a 128-bit IPv6 address. As IPv6 adoption increases among ISPs and carriers, an AAAA record ensures your site remains reachable on modern networks alongside IPv4.
  • CAA: Certificate Authority Authorization record. It specifies which certificate authorities are permitted to issue TLS certificates for your domain. This record helps prevent unauthorized or rogue certificate issuance that could compromise site security.
  • CNAME: Creates an alias from one domain name to another canonical name. It is frequently used to point www.example.com at example.com or to alias subdomains to external services without duplicating underlying records.
  • MX: Mail Exchange record that designates the mail servers responsible for accepting inbound email for the domain. You can specify multiple MX records with different priority values; lower numbers are tried first.
  • SRV: Service record that identifies the hostname, port, priority, and weight for specific services. Commonly required for Microsoft Active Directory, VoIP, or XMPP implementations running on your hosted environment.
  • TXT: Stores arbitrary text strings. Today it is primarily used for SPF, DKIM, and DMARC records to authenticate email senders, as well as for domain ownership validation with third-party services.

#Practical Configuration Examples

DNS records are usually added through the hosting control panel. For advanced users or automated deployments, the same information appears in a zone file. The following example demonstrates all supported record types in standard zone syntax.

example.com.     3600    IN      A       192.0.2.1
example.com.     3600    IN      AAAA    2001:db8::1
example.com.     3600    IN      CAA     0 issue "letsencrypt.org"
www.example.com. 3600    IN      CNAME   example.com.
example.com.     3600    IN      MX      10 mail.example.com.
_service._tcp.example.com. 3600 IN SRV 10 60 5060 sip.example.com.
example.com.     3600    IN      TXT     "v=spf1 include:_spf.google.com -all"

#Common Pitfalls and Best Practices

  • Always set realistic TTL values. Extremely low TTLs increase DNS query load while high values delay propagation of changes; 3600 seconds (1 hour) is a practical default for most records.
  • Never point an MX record at a CNAME target. RFC standards require MX targets to resolve directly to A or AAAA records. Violating this can cause email delivery failures.
  • Validate CAA records before issuing new certificates. An overly restrictive CAA policy can block legitimate certificate renewals from your chosen CA.
  • Test every change with command-line tools such as dig, nslookup, or online DNS checkers immediately after update. Propagation delays and caching at recursive resolvers can mask problems for hours.

Start new domain setups with A (or AAAA) and MX records, then add CNAME, TXT, CAA, and SRV entries only as specific services require them. Verify each record after creation to confirm resolution. For step-by-step instructions on adding records in the control panel, see our guide to managing DNS zones.