What are DNS records?

If you have already read the chapter on how DNS works, you know that the Domain Name System translates domain names into the IP addresses that computers use to find each other. DNS records are the individual entries inside that system. Each record stores a specific piece of information about your domain and what should happen when someone or something tries to reach it.

What are DNS records?

DNS records are entries stored on a name server that tell the internet how to handle requests for your domain. Think of them as a set of directions. One record says where your website files live. Another says where to deliver your email. Another might confirm that you own the domain. Each record has a type, a name, a value, and a TTL (time to live), which controls how long the record is cached before it gets refreshed.

Every domain has at least a few DNS records in place. Without them, nothing connected to the domain works. No website loads, no email gets delivered, and no service can verify that the domain belongs to you.

What are the most common DNS record types?

There are dozens of DNS record types, but most brands will only ever work with six. Each one handles a different job.

A record

The A record is the most basic and most important DNS record. It maps your domain name to an IPv4 address, which is the numerical address of the server where your website is hosted. When someone types your domain into a browser, the A record is what tells the internet which server to connect to. If you are connecting a domain to a hosting provider, the A record is almost always the first thing you set up.

AAAA record

The AAAA record does the same job as the A record, but for IPv6 addresses. IPv6 is the newer version of internet addressing that uses longer addresses to support a much larger number of devices. Not every server uses IPv6 yet, so not every domain needs an AAAA record. If your hosting provider gives you an IPv6 address alongside an IPv4 address, adding an AAAA record ensures your site is reachable on both.

CNAME record

A CNAME record points one domain name to another domain name instead of directly to an IP address. It is commonly used for subdomains. For example, you might set up a CNAME record so that "www.yourdomain.com" points to "yourdomain.com," which itself has an A record pointing to the server. CNAME records create an alias, so if the IP address of the main domain changes, the subdomain automatically follows without needing a separate update.

MX record

MX stands for Mail Exchange. The MX record tells the internet which server handles email for your domain. When someone sends an email to an address at your domain, the sending server looks up the MX record to figure out where to deliver it. If you use a separate email service from your hosting provider, the MX records are how you connect that service to your domain. Without MX records, email sent to your domain has nowhere to go.

TXT record

A TXT record holds plain text data. It is used for a wide range of purposes, but the most common ones are domain verification and email security. When you sign up for a new service and it asks you to "verify your domain," you are usually adding a specific TXT record that the service then checks. TXT records are also used for SPF, DKIM, and DMARC settings, which are email security standards that help prevent spam and phishing from being sent using your domain name.

NS record

NS stands for Name Server. The NS record tells the internet which name servers are responsible for your domain's DNS records. When you register a domain, the registrar sets NS records that point to the registrar's own name servers by default. If you move your DNS management to a different provider, you update the NS records to point to that provider's name servers instead. The NS records are the starting point. Everything else, your A records, MX records, and all the rest, is stored on whichever name servers the NS records point to.

When do you need to edit DNS records?

Most of the time, DNS records are set up once and left alone. But there are a few situations where you will need to make changes.

• Connecting a domain to hosting. When you buy a domain from one provider and host your website with another, you need to update the A record (or sometimes the NS records) to point your domain to the hosting provider's server. This is one of the core steps in understanding domain vs hosting and how the two work together.
• Setting up email. If you want to use a custom email address with your domain, you need to add MX records that point to your email provider's servers.
• Verifying domain ownership. Services like search consoles, email platforms, and SSL certificate providers often ask you to add a TXT record to prove you control the domain.
• Adding a subdomain. If you want to create a subdomain like "shop.yourdomain.com" or "blog.yourdomain.com," you add a CNAME or A record for that subdomain.
• Switching hosting or email providers. Any time you move to a new provider, the DNS records that pointed to the old provider need to be updated to point to the new one.

How do you edit DNS records?

Editing DNS records is done through the provider that manages your domain's name servers. In most cases, that is your domain registrar. Some brands use a separate DNS management service, in which case the edits happen there instead.

The general steps are the same regardless of provider.

1. Log in to the account where your domain's DNS is managed.
2. Find the DNS settings or DNS zone editor for your domain.
3. Choose the record type you want to add or edit (A, CNAME, MX, TXT, etc.).
4. Enter the name (usually the domain or subdomain), the value (the IP address, server name, or text string), and the TTL.
5. Save the record.

Before making any changes, write down the current values of the records you plan to edit. If something goes wrong, having the original values lets you revert quickly instead of waiting for support to look them up for you.

What are common mistakes when editing DNS records?

DNS record changes are simple in concept but easy to get wrong. Here are the mistakes that cause the most problems.

• Editing DNS in the wrong place. If your NS records point to a different provider than your registrar, changes made at the registrar will have no effect. Always confirm where your DNS is managed before making edits.
• Deleting records you did not create. Some records are set up automatically by your hosting or email provider. Deleting them can break your website or email without warning. If you are not sure what a record does, look it up before removing it.
• Using the wrong record type. Adding a CNAME where an A record is needed, or the other way around, will prevent the connection from working. Follow the instructions from your hosting or email provider exactly.
• Forgetting to update MX records after a hosting change. Changing your A record to point to a new host does not affect email. If your email was handled by the old host, your MX records still point there. Update them or your email stops arriving.
• Setting the TTL too high before a planned change. A high TTL means the old record stays cached longer after you make a change. If you know a DNS change is coming, lower the TTL a few hours beforehand so the new record propagates faster once you make the switch.

How long do DNS changes take?

DNS changes do not take effect instantly. After you update a record, the change needs to spread across the internet. This process is called DNS propagation. It can take anywhere from a few minutes to 48 hours, depending on the TTL of the old record and how quickly different internet service providers refresh their cached DNS data.

In practice, most changes propagate within a few hours. During propagation, some visitors may still be directed to the old server while others reach the new one. This is normal and temporary. You can use free online DNS propagation tools to check whether a change has reached specific regions.

If you are planning a major change like switching hosting providers, it helps to lower the TTL on the affected records a day or two in advance. A lower TTL means caches expire faster, so the new record spreads more quickly once you make the change.

How WEMASY handles DNS records

When you connect a custom domain to your WEMASY site, the platform tells you exactly which DNS records to add or update. You get the specific A record values and any other records needed, with step-by-step instructions for where to enter them at your domain registrar. SSL is activated automatically once the domain is connected, and the necessary records for HTTPS are handled on the WEMASY side without additional DNS configuration from you.

For email, WEMASY does not provide email hosting, so your MX records stay pointed at whichever email provider you use. Your website DNS and your email DNS remain independent, which means connecting your domain to WEMASY does not affect your email delivery.

See what is included in each plan at WEMASY pricing.

Frequently asked questions

The next chapter covers how to point a domain to a website, where you will put these DNS records into practice and walk through the full process of connecting a domain to your hosting step by step.