# DNS Records Explained – Configure A, AAAA, MX, TXT & SRV Correctly Complete DNS guide: A, MX, TXT, SRV records, TTL, propagation, Cloudflare, troubleshooting for hosting, email & game servers at NexoraHost. **Quick answer:** DNS (Domain Name System) translates domain names like `myshop.com` into IP addresses computers understand. For hosting, email and game servers you need A, MX, TXT and often SRV records – set correctly they determine reachability, deliverability and performance. This guide is the **complete DNS guide** for hosting, websites, email and game servers – not just a basics explanation. ## Table of contents - [How DNS works](#how-dns-works) - [All DNS record types explained](#record-types) - [Practical examples (website, email, game server)](#examples) - [Choosing TTL correctly](#ttl) - [Understanding DNS propagation](#propagation) - [Cloudflare & DNS](#cloudflare) - [Common errors & troubleshooting](#errors) - [Security & performance](#security) ## How DNS works – step by step When someone visits `nexorahost.com`, this happens: - **Browser queries DNS resolver** (usually your ISP or 1.1.1.1 / 8.8.8.8) - **Resolver queries root server** → "Who manages .com?" - **Resolver queries TLD nameserver** → "Who manages nexorahost.com?" - **Resolver queries authoritative nameserver** → returns A record (IP) - **Browser connects to IP** – website loads This typically takes **20–120 ms**. DNS is therefore a performance factor – slow nameservers = slower first page load. More on nameservers: [Change & configure nameservers](/en/domain/nameserver) ## All DNS record types explained Each record type has its own purpose – nameservers determine where they are managed. TypePurposeExampleWhen do you need it? **A**Domain → IPv4`myshop.com → 93.184.216.34`Website, game server (direct IP) **AAAA**Domain → IPv6`myshop.com → 2001:db8::1`IPv6-capable servers **CNAME**Alias to another domain`www → myshop.com`Subdomains, CDN, Cloudflare **MX**Mail server`mail.myshop.com (priority 10)`Receiving email **TXT**Text records`v=spf1 include:...`SPF, DKIM, DMARC, verification **SRV**Service + port`_minecraft._tcp → mc.server.com:25565`Minecraft, Teamspeak, SIP **NS**Zone nameservers`ns1.nexorahost.de`Set at registrar ## Practical examples ### Example 1: Connect website to web hosting `A @ 93.184.216.34 TTL 3600 A www 93.184.216.34 TTL 3600 # Or: CNAME www myshop.com TTL 3600` Result: visitors reach your website via domain and www subdomain. Then set up SSL: [SSL guide](/en/domain/ssl-einrichten). ### Example 2: Email DNS (SPF + DKIM + DMARC) `MX @ mail.myshop.com Priority 10 TXT @ "v=spf1 mx a -all" TXT default._domainkey "v=DKIM1; k=rsa; p=MIIB..." TXT _dmarc "v=DMARC1; p=quarantine; rua=mailto:admin@myshop.com"` Full guide: [Set up SPF, DKIM & DMARC](/en/domain/spf-dkim-dmarc) ### Example 3: Minecraft server via domain (SRV record) `A mc 192.168.1.100 TTL 3600 SRV _minecraft._tcp mc.myshop.com 0 5 25565 mc.myshop.com` Players connect with `mc.myshop.com` – no port needed. Details: [Minecraft SRV record guide](/en/domain/minecraft-srv-record) ### Example 4: Activate Cloudflare CDN `A @ 93.184.216.34 Proxy ON (orange cloud) CNAME www myshop.com Proxy ON # Never proxy mail records: MX @ mail.provider.com DNS only (grey cloud) TXT @ "v=spf1 ..." DNS only` Cloudflare setup: [Cloudflare DNS guide](/en/domain/cloudflare-dns) ## Choosing TTL correctly – performance vs. flexibility TTLDurationWhen to use? 3005 minBefore server migration, planned DNS changes 36001 hrStandard for most setups 8640024 hrStable records, maximum cache performance **Pro tip:** Lower TTL to 300 48 hours before migration → migrate → after successful propagation raise back to 3600. ## DNS propagation – how long does it really take? - **Normal:** 15–60 minutes (TTL 3600) - **With TTL 300:** 5–15 minutes - **Maximum:** up to 48 hours (rare, usually ISP cache) **Check propagation:** `dig myshop.com +short`, whatsmydns.net, dnschecker.org If old values appear after 48 hours → nameserver or record wrong, not "propagation". ## Cloudflare & DNS – when does it make sense? Cloudflare offers free CDN, DDoS protection and fast DNS (<10 ms). Useful for WordPress/shops with international traffic and Core Web Vitals issues. **Not ideal for:** Pure mail servers (MX must not be proxied), some game server UDP setups. → [Set up Cloudflare](/en/domain/cloudflare-dns) · [Switch nameservers to Cloudflare](/en/domain/nameserver) ## Common DNS errors & troubleshooting ### Website not reachable - Check A record points to correct IP - Nameservers correct? ([Nameserver guide](/en/domain/nameserver)) - Cloudflare: check proxy mode (orange vs grey) - Server firewall: ports 80/443 open? - Waited for propagation? ### Emails not arriving / landing in spam - MX record present and correct? - SPF set? ([SPF guide](/en/domain/spf-dkim-dmarc)) - DKIM enabled at mail provider? - DMARC policy defined? ## Security & performance - **DNSSEC:** Protects against DNS spoofing - **DMARC:** Protects your domain from email spoofing - **Fast nameservers:** Cloudflare, NexoraHost DNS - **Unlimited records at NexoraHost:** No 50–100 record limits like many large hosts ## Related guides - [Domain & DNS hub](/en/domain) - [Change & verify nameservers](/en/domain/nameserver) - [SPF, DKIM, DMARC](/en/domain/spf-dkim-dmarc) - [Cloudflare DNS](/en/domain/cloudflare-dns) - [Minecraft SRV record](/en/domain/minecraft-srv-record) - [Set up SSL/HTTPS](/en/domain/ssl-einrichten) ## FAQ ### What's the difference between A record and CNAME? A record points directly to an IP. CNAME redirects to another domain name – never both for the same name. Root domain (@) technically cannot be CNAME. ### Why does www work but not the root domain? Often the A record for @ (root) is missing. www has CNAME or its own A record, @ doesn't. Set both separately. *Manage domain & DNS: [panel.nexorahost.de](https://panel.nexorahost.de)*