# DNS Record Types Explained ![Cover image for DNS Record Types Explained](https://prod-files-secure.s3.us-west-2.amazonaws.com/1daf8d7b-bd6a-4278-9213-f77aa4198ce5/6d4b7f25-796a-4966-87a8-bc0a8bc142f1/1820e4a9-0584-4588-8cb2-54f3a0b287b4.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=ASIAZI2LB466TVH47Y7C%2F20261101%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20261101T133151Z&X-Amz-Expires=3600&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEJr%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLXdlc3QtMiJHMEUCIFXJ6jdw6xnJ8JpHMMA7m5OX9fdmFawvL3rnZS%2B8oon4AiEAlE24QI1Pi5RZt%2F7hv2fdURJz7t9fy89rlDy%2BtNFCRMwq%2FwMIYhAAGgw2Mzc0MjMxODM4MDUiDBVkW2ojL%2BdVPt1TXyrcAylPBzoo0SmC9AnD922gwJN1yQSF7xKBAHE490%2B96eChWBveiDHbbRFFBvs7Rvzm2RBku1fP%2BkN9WbfjSFZt7MSNnvM72UKK5sBoj3AInLLPjCkWaiOB3Uba125etbHisXpsZ%2BXeFNk6LST57g%2Bj1oP61QgGMATVmO8fRn9r3l7iJ1Q90d2vn9xCq9rrhG0Eni%2FmHuqtW6rVpnM%2FUa%2B77pU0E%2BTsOhGA6thYgnENRrixsiyxmbRLuNBUb2tBPIo0ehcdANiv2XdmUEGb6unpgFJ7p37IPQ5IXs%2ByFOOeIR%2FiwZOjveekWcU9QsUJTe0%2BGPD4016NQeeC6sXyGaendhO8oecQIlZuE33JbfKNl1av%2F%2F9JjyxCJC2xcM1o3KWc%2BU2daM9DClwan1hb%2BE5qWoeWOpkFXiSBfWeTrysnCvloDNvQMxl4tipOPMg6Wx%2B2HFJn5mJEXt899AOVXow9MDUfAWxGmeK%2FzT1MARf%2FgTR%2FI3UV%2FAcx%2FnUnLESdyDAWuMrRtSl8AZ22rT9%2Feac4Ien8so5o439Nc3lqWHr3M062s4LWStN4ipWBk6OcEdG7yXa9CquwtsZYl4nr8%2Fxgi84aYaK9%2F3hPLnQZI0rUvV5ZwUVCSPnItA7zKgRBMOiUnNcGOqUBLl%2F4w%2BPesLGUilrObo7BWDhcHZkn3pxn7NSDuTOpXjWI2W6MLNVEFT4nxr10v9ekijPpZTQTQqahnCB2jzUYIqJ6I5raBRhPf9YSlScdQ8kafjeq9vinRbgheQ5f%2BhUzA9oIQTCIkpLM9%2BCN92MSe1x9QhXyeo9Vtdi5TtmuZz%2B38dxdlFV69xMYGEyJ7Xc04N37V1CsCKnWdKsaYByynb961Ah3&X-Amz-Signature=fe730f23b31546ce12f1ace350582dc0941b12859ef8fcb26dff5fef72afc5dd&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject) ## A Beginner-Friendly Guide to DNS Record Types How the internet figures out where your website actually lives --- When you buy a domain and open your DNS dashboard, it feels like stepping into a room full of cryptic acronyms — A, AAAA, CNAME, MX, TXT, NS. It looks chaotic, but everything follows a very simple logic. It all starts with the basic question: When I type a website name into my browser, how does the browser know where that site actually lives? That’s the job of DNS. --- ## What is DNS? (Think of it as the Internet’s Phonebook) Computers don’t understand names like google.com. They only understand numbers — IP addresses. Remembering numbers for every website would make the internet unusable. DNS — Domain Name System — is the phonebook of the internet. - You type a domain name - DNS returns the right IP address - Your browser goes to that address - Website loads That’s the whole flow. ![Illustration accompanying: What is DNS? (Think of it as the Internet’s Phonebook)](https://prod-files-secure.s3.us-west-2.amazonaws.com/1daf8d7b-bd6a-4278-9213-f77aa4198ce5/7bb6870f-72eb-4002-838f-35a76e39856c/5e5dbfef-69c7-45ec-a1ca-0dacebe835ff.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=ASIAZI2LB466TVH47Y7C%2F20261101%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20261101T133151Z&X-Amz-Expires=3600&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEJr%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLXdlc3QtMiJHMEUCIFXJ6jdw6xnJ8JpHMMA7m5OX9fdmFawvL3rnZS%2B8oon4AiEAlE24QI1Pi5RZt%2F7hv2fdURJz7t9fy89rlDy%2BtNFCRMwq%2FwMIYhAAGgw2Mzc0MjMxODM4MDUiDBVkW2ojL%2BdVPt1TXyrcAylPBzoo0SmC9AnD922gwJN1yQSF7xKBAHE490%2B96eChWBveiDHbbRFFBvs7Rvzm2RBku1fP%2BkN9WbfjSFZt7MSNnvM72UKK5sBoj3AInLLPjCkWaiOB3Uba125etbHisXpsZ%2BXeFNk6LST57g%2Bj1oP61QgGMATVmO8fRn9r3l7iJ1Q90d2vn9xCq9rrhG0Eni%2FmHuqtW6rVpnM%2FUa%2B77pU0E%2BTsOhGA6thYgnENRrixsiyxmbRLuNBUb2tBPIo0ehcdANiv2XdmUEGb6unpgFJ7p37IPQ5IXs%2ByFOOeIR%2FiwZOjveekWcU9QsUJTe0%2BGPD4016NQeeC6sXyGaendhO8oecQIlZuE33JbfKNl1av%2F%2F9JjyxCJC2xcM1o3KWc%2BU2daM9DClwan1hb%2BE5qWoeWOpkFXiSBfWeTrysnCvloDNvQMxl4tipOPMg6Wx%2B2HFJn5mJEXt899AOVXow9MDUfAWxGmeK%2FzT1MARf%2FgTR%2FI3UV%2FAcx%2FnUnLESdyDAWuMrRtSl8AZ22rT9%2Feac4Ien8so5o439Nc3lqWHr3M062s4LWStN4ipWBk6OcEdG7yXa9CquwtsZYl4nr8%2Fxgi84aYaK9%2F3hPLnQZI0rUvV5ZwUVCSPnItA7zKgRBMOiUnNcGOqUBLl%2F4w%2BPesLGUilrObo7BWDhcHZkn3pxn7NSDuTOpXjWI2W6MLNVEFT4nxr10v9ekijPpZTQTQqahnCB2jzUYIqJ6I5raBRhPf9YSlScdQ8kafjeq9vinRbgheQ5f%2BhUzA9oIQTCIkpLM9%2BCN92MSe1x9QhXyeo9Vtdi5TtmuZz%2B38dxdlFV69xMYGEyJ7Xc04N37V1CsCKnWdKsaYByynb961Ah3&X-Amz-Signature=79767a8a73e5298eb80ab1b8e2c6dedd71555955cd5babad9db8599a58827c4a&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject) --- ## Why Do We Need Different DNS Records? A domain doesn’t just serve a website. It may: - Handle email - Host subdomains - Redirect visitors - Prove domain ownership - Work with external services So DNS needs different record types — just like a business might have: - Main number - Support number - Fax number - Mailing address Each DNS record solves one specific problem. Let’s break them down simply. --- ## 1. NS Record (Name Server) “Who is responsible for this domain?” Before the internet can fetch any details about your domain, it needs to know which DNS provider stores your records. That pointer is the NS record. Changing NS records = switching your entire DNS “manager.” Analogy: The signboard in a library telling you which section has the book you need. --- ## 2. A Record “Where is the website server?” The A Record maps a domain name to an IPv4 address. Example: mycoolsite.com → 192.0.2.1 If this record is missing, your domain leads nowhere. Analogy: The street address of your house. --- ## 3. AAAA Record “Where is the server (using IPv6)?” IPv4 addresses are running out. IPv6 solves that. AAAA Records behave exactly like A Records — but use IPv6. Most modern websites use both. Analogy: Same house address but written in long GPS coordinates. --- ## 4. CNAME Record “I want different names to go to the same place.” Examples: - www.mycoolsite.com → mycoolsite.com - blog.mycoolsite.com → external-blog-host.com A CNAME maps one name to another name, not to an IP. Browser sees a CNAME and says: “Go look up this other name instead.” Analogy: A nickname — Bobby → Robert. Quick clarity: - A Record: name → number - CNAME: name → name --- ## 5. MX Record “Where should emails for this domain go?” Your email server is usually different from your website server. MX Records tell the internet: “Send all emails for this domain to this mail server.” Example: @ → smtp.google.com Also supports priorities (backup mail servers). Analogy: A special P.O. box. You don’t drop mail at the shop—you send it to the mailbox. Quick clarity: - NS = who controls DNS - MX = who handles your email --- ## 6. TXT Record “I need to prove I own this domain.” TXT records don’t route traffic. They store text notes used for: - Google verification - Vercel/Netlify ownership checks - Email security (SPF, DKIM, DMARC) Analogy: Showing your ID or leaving instructions for a delivery driver. --- ## How All DNS Records Work Together A typical small website DNS setup: | Record | Host | Value | Purpose | | --- | --- | --- | --- | | NS | @ | ns1.bluehost.com | Bluehost manages DNS | | A | @ | 192.0.2.55 | Main website server | | CNAME | www | mycoolsite.com | www → root domain | | MX | @ | smtp.google.com | Email server | | TXT | @ | google-site-verification=xyz | Proof of ownership | Each piece handles one job. Together, they make your domain functional, reachable, and secure. --- ## Final Note DNS looks complicated only on the dashboard. In reality, it’s: - Names → Addresses - Pointers → Servers - A few simple records working together Once this foundation is clear, digging deeper into resolvers, caching, and TTL becomes a natural next step in the story.