A domain can be registered, a website can be fully built, and business email can be ready to go – yet none of it works until DNS points visitors and messages to the right place. Learning how to configure DNS records gives you control over that connection, whether you are launching your first site, moving hosting, or setting up a new email provider.
DNS changes are not difficult once you understand what each record does. The risk comes from changing the wrong record, deleting an existing email setting, or assuming an update will appear everywhere immediately. A careful process protects your website, keeps mail flowing, and avoids a stressful support ticket at the worst possible time.
What DNS Records Actually Control
DNS, or Domain Name System, works like the directory for your domain. When someone enters your domain name into a browser, DNS tells that browser which server should answer. When a customer emails you, DNS tells their mail server where to deliver the message.
Your DNS zone is a collection of records. Each record has a purpose: connecting a root domain to a website, directing a subdomain, verifying ownership with a third-party tool, or setting rules for email delivery. Your domain registrar, hosting provider, or DNS service may manage the zone. Before making changes, confirm which one is authoritative.
This distinction matters. If your domain uses nameservers from your hosting provider, editing DNS at the registrar may have no effect. For example, if your domain points to GiddyHost nameservers, make the change in the DNS zone managed there rather than in an old registrar dashboard.
The DNS Records You Will Use Most Often
You do not need to memorize every DNS record type. Most website owners regularly work with a small set.
A Records Point Domains to an IPv4 Address
An A record connects a name to an IPv4 address, such as `192.0.2.10`. It is commonly used for the root domain, represented by `@`, and sometimes for a subdomain such as `shop` or `app`.
If you move a website to a new server, the A record is often the setting that must change. Use the exact IP address supplied by your hosting provider. A single misplaced digit can send visitors to an error page or an unrelated server.
CNAME Records Create Aliases
A CNAME record makes one hostname behave like another hostname. The classic example is pointing `www.yourdomain.com` to `yourdomain.com`. It is also common when connecting a subdomain to services such as a store platform, scheduling tool, or marketing system.
A CNAME should point to a hostname, not an IP address. Also, the root domain usually cannot use a standard CNAME because it must coexist with other records. Some DNS providers offer special flattening features, but do not rely on that behavior unless your provider specifically supports it.
MX Records Route Your Business Email
MX records tell other mail servers where to send messages addressed to your domain. They include a destination hostname and a priority number. Lower numbers have higher priority.
When setting up professional email, enter every MX record your provider gives you, including the correct priorities. Do not leave old MX records in place unless your provider tells you to. Mixed records can cause messages to arrive inconsistently or go to a retired mailbox.
TXT Records Verify Ownership and Protect Email
TXT records store text-based instructions. You may add one to verify your domain with Google, Microsoft, a payment provider, or another service. TXT records are also essential for email authentication.
SPF identifies servers allowed to send email for your domain. DKIM adds a cryptographic signature that helps receiving providers validate legitimate mail. DMARC tells receiving servers what to do when SPF or DKIM checks fail and gives you visibility into authentication results.
Email authentication is not optional for a growing business. Without it, legitimate invoices, contact-form replies, and sales messages are more likely to land in spam. Be careful with SPF, though: your domain should have only one SPF TXT record. If you use multiple sending services, their permitted sources must be combined into one policy.
AAAA and SRV Records Have More Specialized Roles
AAAA records work like A records but point to an IPv6 address. Add one only when your host or service provides an IPv6 address and instructs you to use it.
SRV records are less common for standard websites, but may be required for communications platforms, game servers, or certain Microsoft services. They use a precise format with service names, ports, priorities, weights, and targets. Copy these values exactly instead of trying to simplify them.
How to Configure DNS Records Safely
The safest DNS update starts before you log in. Write down what you are changing, why you are changing it, and the exact values provided by the new service. Take a screenshot or export of the current DNS zone. That backup makes recovery far easier if you need to reverse a change.
1. Find the Active DNS Provider
Log in where your domain is registered and look at the nameservers. If they are the registrar’s default nameservers, DNS may be managed there. If they reference your host, Cloudflare, or another provider, use that provider’s DNS dashboard instead.
Do not change nameservers just to add one record. Replacing nameservers can overwrite the connection to your website, email, verification tools, and subdomains. Edit the active zone whenever possible.
2. Check for Existing Records Before Adding New Ones
Search the DNS zone for the hostname you plan to use. If an A record already exists for `www`, adding a second conflicting A record can create unpredictable results. If an old CNAME occupies that name, you must usually edit or remove it before creating a new one.
The same caution applies to mail. Review all MX and TXT records before changing email providers. Website and email DNS can coexist, but both need their own correct entries.
3. Enter the Host, Value, and TTL Carefully
Most DNS dashboards ask for a host or name, a record type, a value or target, and a TTL. The host is often `@` for the main domain, while `www`, `mail`, or `shop` represents a subdomain.
TTL stands for Time to Live. It tells resolvers how long they can cache the answer. For a planned migration, lowering the TTL to 300 seconds a day before the move can help changes spread more quickly. After the migration is stable, returning it to 3600 seconds is a reasonable default for many sites.
A lower TTL does not guarantee instant worldwide updates. It only reduces future caching time. Some networks, browsers, and local devices may still show an older result for a while.
4. Save, Then Verify the Exact Result
After saving a record, revisit the DNS zone and compare the visible entry with the instructions you received. Watch for dashboards that automatically append your domain name. Entering `www.yourdomain.com` in a host field that expects only `www` may accidentally create `www.yourdomain.com.yourdomain.com`.
Then test the service itself. Open the website using a private browser window, send a message to and from your business address, or complete the verification check in the connected platform. A DNS lookup tool or command-line query can confirm the record publicly, but real-world testing confirms the service works as intended.
Common DNS Mistakes That Cause Avoidable Problems
The most common mistake is deleting records that seem unfamiliar. A random-looking TXT record may be a verification token. An MX record may be keeping your email online. Before removal, identify its owner and purpose.
Another mistake is editing the domain’s nameservers when the real need is a single A or CNAME record. Nameserver changes are broader and can take longer to propagate. They should be reserved for moving all DNS management to another provider.
It also helps to avoid making several unrelated changes at once. If you update hosting, email, and a subdomain in one session, troubleshooting becomes harder. Make a change, verify it, then move to the next task.
Finally, do not panic if a correct update is not visible immediately. DNS propagation often completes within minutes, but may take up to 24 to 48 hours depending on prior TTL values and resolver caching. If the record is correct in the authoritative zone, give the change time before making repeated edits.
Plan DNS Changes Around Your Business
For a simple new website, configuring DNS can be a quick task. For a live business with customer email, order notifications, and marketing platforms, treat it as a planned change. Schedule migrations during lower-traffic hours, keep the old hosting account active until the new site is confirmed, and test email from more than one provider.
If you are unsure whether a record is safe to change, pause before saving. The best DNS setup is not the most complicated one. It is the one that points every service where it belongs, protects your email reputation, and gives your customers a dependable way to reach you.