On this page
Definition
Nameservers are specialised DNS servers that tell the internet where to find the DNS records for a domain name. They do not usually host your website or email themselves. Instead, they point browsers, mail servers and other services to the correct DNS zone for your domain.
If nameservers are wrong, unavailable or changed without planning, your website, email, SSL validation and connected services can stop working.
Key Takeaways About Nameservers
- Nameservers direct DNS lookups to the place where your domain's DNS records are managed.
- They affect websites, business email, SSL certificates, verification records and many third-party tools.
- Nameserver changes should be planned carefully, especially during website, hosting, email or domain migrations.
Quick Explanation
What Nameservers Do
DNS Basics
Nameservers Are Not the Same as DNS Records
Nameservers vs DNS Records
The distinction is important during migrations, troubleshooting and provider changes. Many website and email outages happen because nameservers and DNS records are treated as though they are interchangeable.
| Area | Nameservers | DNS Records |
|---|---|---|
| Main purpose | Tell the internet where the domain's DNS zone is managed. | Tell services where to send website, email and verification traffic. |
| Common examples | Cloudflare nameservers, registrar nameservers or hosting provider nameservers. | A, AAAA, CNAME, MX, TXT, SPF, DKIM and DMARC records. |
| Risk when changed | The internet may start reading a different DNS zone entirely. | One specific service may break if a required record is missing or incorrect. |
How It Works
How a Nameserver Lookup Works
The full DNS process involves several systems, but the basic pathway can be understood in a few steps. This is a simplified explanation of what happens when someone tries to visit a website.
-
A user enters the domain
A person types a domain into a browser or clicks a link. The device needs to find the server connected to that domain.
-
DNS looks for the authoritative nameservers
DNS resolvers check where the domain's authoritative DNS information is managed. The nameservers identify the correct DNS zone to ask.
-
The DNS record provides the destination
The relevant record, such as an A record or CNAME record, tells the browser where to send the website request. For email, an MX record would be used instead.
Example DNS Zone Snapshot
This example shows how nameservers and DNS records work together. The nameservers identify where the DNS zone is hosted. The records inside that zone provide the specific instructions for website and email services.
Nameservers:
ns1.example-dns.com
ns2.example-dns.com
DNS records inside the zone:
A @ 203.0.113.10
CNAME www example.com.au
MX @ mail.protection.outlook.com
TXT @ v=spf1 include:spf.protection.outlook.com -allExample only. Real records depend on the website, email platform, registrar and connected services.
Business Impact
Why Nameservers Matter for Websites, Email and Trust
Changing Nameservers Changes Where DNS Is Read
Key Nameserver and DNS Terms
These terms often appear together when domains, websites and email systems are being configured or moved.
- Authoritative nameserver
- A nameserver that holds or directs queries to the official DNS information for a domain.
- DNS zone
- The collection of DNS records for a domain, usually managed through a registrar, DNS provider, hosting provider or platform such as Cloudflare.
- TTL
- Time to live. This tells DNS resolvers how long they may cache a record before checking for an updated version.
Common Nameserver Problems
Nameserver faults often appear as website, email or SSL problems. The visible symptom may not clearly mention DNS, so diagnosis needs to consider the whole domain setup.
The website stops loading after a provider change.
Likely cause
The domain may have been pointed to new nameservers, but the new DNS zone may not contain the correct A, AAAA or CNAME records.
Solution
Compare the previous DNS zone with the new one, confirm the correct hosting destination, then update the missing or incorrect records.
Business email stops working after a website launch.
Likely cause
The nameserver change may have moved DNS management away from a zone that contained the required MX and TXT records.
Solution
Restore or recreate the email records in the active DNS zone, then test sending, receiving and authentication.
Different users see different website results.
Likely cause
DNS caching and propagation can mean some networks still use older information while others use newer records.
Solution
Check the current authoritative nameservers and DNS records, then allow for propagation while monitoring the affected services.
Nameserver Mistakes to Avoid
Most nameserver mistakes are avoidable with documentation, access checks and a planned migration process. The risk increases when domains, hosting and email are managed by different providers.
Changing nameservers without copying all DNS records.
Do this instead
Document the active DNS zone first, including website, email, TXT verification, SPF, DKIM, DMARC and any third-party records.
Assuming the website host controls every DNS setting.
Do this instead
Confirm where the domain is registered, which nameservers are active and which provider manages the DNS zone.
Making DNS changes during a busy trading period.
Do this instead
Schedule changes at a sensible time, lower TTL values where appropriate and have rollback information ready before starting.
Nameserver Change Checklist
Use this checklist before changing nameservers or moving DNS management to a new provider.
-
Confirm domain access and ownership
Make sure the registrar account is accessible and that the domain is registered to the correct business or authorised registrant.
-
Copy and verify the existing DNS zone
Record all A, CNAME, MX, TXT, SPF, DKIM, DMARC and platform verification records before making changes.
-
Test after propagation begins
Check the website, email sending and receiving, SSL status, forms and connected tools after the change is made.
Managing Nameservers Internally
When It Can Work
- Straightforward domains with one simple website and no complex email setup may be manageable by an internal administrator.
- Small record updates can often be handled safely when the current DNS zone is well documented.
- Internal control can be convenient if the business has reliable technical knowledge and access governance.
Risks to Consider
- A single missing MX or TXT record can interrupt business email or authentication.
- Provider changes can become confusing when the registrar, DNS, hosting and email accounts are separate.
- Troubleshooting can take longer if previous DNS records were not documented before changes were made.
When to Review
When Nameservers Should Be Checked
Our Approach
How We Approach Nameservers and DNS
Nameserver FAQs
These quick answers cover common questions business owners ask when dealing with domains, hosting and email setup.
Are nameservers the same as website hosting?
Will changing nameservers break my email?
How long do nameserver changes take?
Need Help Reviewing Your Domain or DNS Setup?
If your domain, website, hosting and email setup feels unclear, we can review the current configuration and explain the practical risks before changes are made. This is especially useful before a migration, launch or email platform change.