DNS Records

DNS records explained, the settings that point your domain at your site

What are DNS records and how do they work?

DNS is the system that turns your domain name into the server address browsers actually connect to. You control it through records: an A record points your domain at an IP address, a CNAME aliases one name to another, MX records route your email, and TXT records hold verification and policy data. Name servers decide which provider holds these records for your domain.

Jump to the tools Back to home

The records you will actually use

DNS (the Domain Name System) is the internet's address book. When someone types your domain, DNS looks up which server to contact and returns its numeric IP address. You shape that lookup with a handful of record types. The A record maps your domain to an IPv4 address (an AAAA record does the same for IPv6). A CNAME record points one hostname at another name rather than an IP, which is how subdomains like www are usually aliased to the main domain.

MX (mail exchange) records tell the world which mail servers handle email for your domain, so they are what you edit when you set up email or move to a new provider. TXT records store text, and they have become essential for verifying domain ownership with services like Google and Facebook, and for email authentication records such as SPF, DKIM, and DMARC that help your mail reach inboxes. NS (name server) records declare which DNS provider is authoritative for your domain.

Name servers and why changes take time

Your domain's name servers decide where its DNS records live. By default that is usually your registrar, but you can point the name servers at your host or a dedicated DNS provider, after which you manage records in that provider's control panel. Changing name servers is how you connect a domain bought at one company to hosting at another; it is the single most common setup step for a new site.

DNS changes are not instant. Each record carries a TTL (time to live) that tells other servers how long to cache it, so an update can take anywhere from minutes to a day or two to be seen everywhere as old cached copies expire. This is called propagation. If you change a record and the old value lingers, you are almost always just waiting on propagation, not looking at a mistake. Lowering a record's TTL before a planned change makes future updates take effect faster.

What to check

What to look for

Act on this

Tools to act on this guide

Each slot below is reserved for a host, registrar, or tool we would use ourselves. We are adding them as we vet them; nothing here is a paid placement.

Reserved slot DNS record manager

Where readers edit A, CNAME, MX, and TXT records.

Reserved slot DNS lookup and checker tool

Verify current records and propagation.

Reserved slot Name server setup guide

Connecting a domain to hosting elsewhere.

Questions

Frequently asked questions

What is an A record in DNS?
An A record maps a domain or subdomain to an IPv4 address, telling browsers which server to connect to for that name. It is the most fundamental DNS record, the one you set to point your domain at your hosting. The AAAA record does the same job for newer IPv6 addresses, and many sites have both.
What is the difference between an A record and a CNAME?
An A record points a name directly at a numeric IP address. A CNAME points a name at another name instead, which then resolves to an IP. You use an A record for your main domain at your server's IP, and a CNAME to alias something like www or a subdomain to that main name without repeating the IP.
What are MX and TXT records used for?
MX (mail exchange) records tell other mail servers which servers handle email for your domain, so you edit them when setting up or moving email. TXT records store text values, now widely used to verify domain ownership with services like Google and Facebook and to hold SPF, DKIM, and DMARC records that improve email deliverability.
Why do DNS changes take so long to work?
DNS records are cached across the internet according to each record's TTL (time to live), so after you change one, other servers keep serving the old value until their cache expires. This propagation can take from a few minutes to a day or two. Lowering the TTL before a planned change makes the next update apply faster.
What are name servers?
Name servers are the authoritative source for your domain's DNS records. The NS records on your domain declare which provider holds those records, whether your registrar, your host, or a separate DNS service. Pointing your name servers at a provider is how you choose where you manage DNS, and how you connect a domain to hosting at another company.

1 Free Website is reader-supported. Some links on this site are affiliate links, which means we may earn a small commission when you sign up through them, at no extra cost to you. We only point to hosts, registrars, and tools we would use to launch our own site.