Your domain can be registered in one place, hosted in another, and use email from a third provider. That setup works well, but only if the DNS is pointed correctly. This guide to domain DNS settings explains what to change, what to leave alone, and how to avoid taking your website or email offline during the process.
DNS may look technical because of the record names and values, but the job is simple: DNS tells visitors and services where your domain should go. Once you know which company controls your DNS and which record handles each service, most updates take only a few minutes.
What domain DNS settings actually control
DNS stands for Domain Name System. Think of it as the directory for your domain name. When someone enters your domain in a browser, DNS directs that request to the server hosting your website. It also tells email providers where to deliver messages and helps verify services such as email marketing platforms, Google Workspace, and Microsoft 365.
Your DNS settings are usually managed in one of two places: at your domain registrar or in your hosting account. If your domain uses your hosting provider’s nameservers, you will normally manage records through the hosting control panel. With cPanel hosting, that is often the Zone Editor.
Before changing anything, confirm where your DNS is active. Editing records in the wrong account will not affect your live domain. More importantly, changing nameservers without copying existing records can disconnect email, website tools, or other services that already depend on them.
Nameservers vs. DNS records
Nameservers and DNS records are related, but they do different jobs.
Nameservers determine who has authority over your domain’s DNS zone. For example, if you point a domain to your hosting provider’s nameservers, that hosting provider becomes the place where you manage the domain’s DNS records.
DNS records are the individual instructions inside that zone. They point web traffic, email, subdomains, and service verifications to the right destination.
A common mistake is changing nameservers when a service provider only asked you to add a record. If you are connecting an email platform or verifying a domain with a third-party tool, you usually need to add a TXT, CNAME, or MX record instead. Only change nameservers when you are moving DNS management or when your hosting provider specifically instructs you to do so.
The DNS records most website owners use
You do not need to memorize every DNS record type. Most small websites only use a handful, and each has a clear purpose.
- A record: Points a domain or subdomain to an IPv4 server address. Your main website often uses an A record for `@`, which represents the root domain.
- AAAA record: Does the same job as an A record, but points to an IPv6 address. Do not add one unless your hosting provider gives you the correct IPv6 address.
- CNAME record: Points one hostname to another hostname. The `www` version of a domain commonly uses a CNAME that points to the root domain.
- MX record: Directs incoming email to your mail provider. These records are essential if you use business email.
- TXT record: Stores text-based verification and security information. It is commonly used for SPF, DKIM, domain ownership verification, and other email authentication settings.
- SRV record: Helps certain communication and application services find the correct server and port. You may see it when setting up specialized email or phone services.
The record name, value, priority, and TTL must match the instructions you receive. A single missing character can prevent a record from working, so copy values carefully and do not add extra quotation marks unless the provider specifically requests them.
How to update DNS settings safely
Start by writing down what you are trying to connect. Is it a new hosting account, a website builder, professional email, or a verification service? The answer determines whether you need to change nameservers or add a specific record.
1. Check your current DNS setup
Log in to the account where your domain is registered and look for the current nameservers. If they point to your web host, sign in to the hosting account and open the DNS management area. In cPanel, look for Zone Editor or a similarly named DNS tool.
Review the existing records before editing. Take a screenshot or copy the current entries into a document. This is especially useful when your domain already receives email. If something goes wrong, you will have a reference for restoring the previous configuration.
2. Use the instructions from the service you are connecting
Hosting providers, email providers, and website platforms typically give exact DNS values. Follow those values rather than trying to translate them from another setup guide.
For a website move, you may receive a new server IP address and be asked to update the A record. For an external email provider, you may receive several MX records plus TXT records for SPF and DKIM. For domain verification, you may only need one TXT or CNAME record.
Pay close attention to the host or name field. Some DNS tools expect `@` for the main domain, while others use a blank field. For a subdomain such as `shop.yourdomain.com`, the host may be entered as `shop` rather than the full domain name. The right format depends on the DNS panel, so read the field labels before saving.
3. Remove conflicting records only when needed
Adding a new record is not always enough. A conflicting A record, CNAME, or MX record can send traffic to the wrong place.
For example, a hostname should not normally have both a CNAME record and another record type such as an A record. Similarly, replacing your email provider’s MX records with a new set may stop mail delivery through the old provider. Do not delete existing entries unless you know they are being replaced.
If you are unsure, support is worth contacting before making the change. A short check can prevent lost email or unnecessary website downtime.
4. Set a practical TTL
TTL means Time to Live. It tells DNS resolvers how long they can keep a saved copy of a record before checking for an update. TTL is measured in seconds.
A lower TTL, such as 300 seconds, can be useful before a planned website or email migration because changes may be picked up faster. A higher TTL can reduce repeated lookups once your setup is stable. For most small websites, the default value is fine. The key is consistency and avoiding last-minute changes without allowing time for propagation.
Why DNS changes do not always work immediately
After you update DNS, the change must spread through DNS resolvers around the internet. This process is called propagation. Some updates appear within minutes, while others can take several hours. Nameserver changes may take up to 24 to 48 hours in some cases.
During that period, one visitor may see the new website while another still reaches the old server. This is normal. Repeatedly changing records while waiting can make troubleshooting harder and extend the confusion.
If a change still does not work after the expected time, check the record type, host field, value, and any required priority. Also confirm that the domain is using the nameservers for the DNS zone you edited. These are the most common causes of failed DNS updates.
DNS settings that protect email delivery
If your domain sends business email, DNS is part of your reputation. Three records matter most: SPF, DKIM, and DMARC.
SPF identifies which servers are allowed to send mail for your domain. DKIM adds a signed key that helps receiving servers verify that a message was not altered. DMARC tells receiving providers how to handle messages that fail those checks and can send reports about unauthorized activity.
These records reduce spoofing and improve the chance that legitimate messages reach the inbox. The exact values depend on your email provider, so use its instructions and avoid combining separate SPF records. A domain should generally have one SPF TXT record, even if it authorizes more than one sending service.
A practical checklist before you save
Before making a DNS update, confirm that you are editing the active DNS zone, using the exact record type requested, and entering the correct host and value. If email is involved, verify whether the change replaces existing MX records or adds to them. Keep a copy of the original entries, then give the update time to propagate before deciding it failed.
DNS is one of the few settings that can affect your website, email, and connected tools at once. A careful change keeps everything working as intended. When you need a reliable place to manage hosting and DNS without unnecessary complexity, a cPanel-based setup such as Visiba gives you clear controls and expert support when you need a second set of eyes.