We talking about Cloud
Web Hosting & Cloud Services
Celebrate the power and freedom of Open Source
with Open Source Cloud Servers starting at only £10/mo £5/mo.
Web Hosting & Cloud Services
Celebrate the power and freedom of Open Source
with Open Source Cloud Servers starting at only £10/mo £5/mo.
Knowing how to change DNS zones helps when you move a website, connect a subdomain or switch email providers. In cPanel, go to Domains → Zone Editor → Manage beside your domain, then edit the record you need.
Before making any changes, check where your domain’s DNS is managed. Your website can be hosted with DigitalBerg while another provider manages its DNS records. Editing the wrong DNS dashboard will not change what visitors see.
Your domain’s authoritative nameservers publish the DNS records the internet uses. Check the nameservers listed in your domain registrar account and compare them with your hosting or DNS provider’s instructions.
For example:
Changing DNS records and changing nameservers are different tasks. Moving a website often requires only an address-record change. Moving the entire DNS service requires copying and checking all relevant records before changing nameservers.
Before you start, save the existing records so you can restore them if necessary.
Each record type has a specific purpose.
| Record | What it does | Example |
|---|---|---|
| A | Points a hostname to an IPv4 address | example.com → 192.0.2.10 |
| AAAA | Points a hostname to an IPv6 address | example.com → 2001:db8::10 |
| CNAME | Makes one hostname an alias of another | www.example.com → example.com |
| MX | Identifies incoming email servers | example.com → mail.example.com |
| TXT | Stores verification or email-authentication information | A provider-supplied verification token |
| NS | Identifies authoritative nameservers | Your DNS provider’s nameserver hostname |
The addresses above are examples. Use the exact settings supplied by your hosting, email or application provider.
A website move does not necessarily require changes to email records. Keep unrelated records in place.
Follow these steps to update a record:
Before saving, double-check the hostname. Some interfaces append your domain automatically. An entry such as www.example.com.example.com usually indicates that the domain was added twice.
Do not enter https:// or a page path in a hostname field.
Available options depend on the features enabled for your account. If a record type is missing, contact support rather than resetting the zone.
For interface details, see the official cPanel Zone Editor documentation.
An A record connects a hostname to an IPv4 address.
For example:
Name: example.com.
Type: A
Value: 192.0.2.10
TTL: Use the value agreed for your migration
Replace the example address with your server’s actual IP address.
If you are replacing an existing server, edit the relevant record rather than adding another address unintentionally. Multiple A records can be valid, but they should be part of a deliberate configuration.
Also check:
www hostname: it may have its own A record or a CNAME.DNS points visitors towards the server. It does not configure the website on that server.
wwwA CNAME makes one hostname an alias of another.
Name: www.example.com.
Type: CNAME
Target: example.com.
The target must be a hostname, not an IP address or a full URL.
A standard CNAME cannot coexist with other ordinary record data at the same hostname. It is also generally unsuitable at the zone root, where other required records exist. Some DNS providers offer special alias or flattening features; follow their instructions.
A CNAME does not redirect a browser from one web address to another. Browser redirects are configured through your website or web server.
Read more about CNAME records and their restrictions.
MX records identify the servers that receive email for your domain.
Name: example.com.
Type: MX
Priority: 10
Destination: mail.example.com.
This is an illustrative example, not a complete email configuration.
Use every MX record supplied by your email provider, including its priority. Lower priority numbers are preferred. Multiple records may be intentional, so do not remove backup entries without checking.
An MX destination should be a mail-server hostname, not a raw IP address. If you use your own hostname, such as mail.example.com, it needs suitable address records.
After changing MX records, review cPanel → Email → Email Routing:
If you are unsure, ask your hosting provider to confirm the setting. Incorrect routing can disrupt mail delivery even when the public MX records look correct.
See cPanel’s Email Routing documentation.
Services may ask you to add a TXT record to verify domain ownership or configure email authentication.
Copy the supplied record type, hostname and value carefully. A verification token, SPF policy and DMARC policy serve different purposes; one does not replace another.
For SPF:
DKIM may use TXT or CNAME records, depending on the provider. Preserve the supplied selector and destination or key.
For background, see how SPF records work.
TTL, or time to live, tells a DNS cache how long it can reuse an answer.
For example:
| TTL | Duration |
|---|---|
300 |
Five minutes |
1800 |
Thirty minutes |
3600 |
One hour |
86400 |
One day |
A five-minute TTL does not guarantee that every visitor will see a change within five minutes. Some resolvers may still hold an older answer with the previous TTL.
For a planned migration:
For example, reducing a one-day TTL immediately before changing an IP address does not clear answers already cached for a day.
Nameserver changes and negative caching can involve other delays. Instead of assuming every change takes a fixed number of hours, compare the authoritative answer with cached answers.
Learn more about TTL and caching.
Saving a record is only the first check. Confirm that public DNS returns the expected answer, then test the service itself.
If you have dig installed, replace example.com in these commands with your domain:
dig NS example.com +short
dig A example.com +short
dig AAAA example.com +short
dig CNAME www.example.com +short
dig MX example.com +short
dig TXT example.com +short
To query an authoritative server directly:
dig @ns1.example.net example.com A +noall +answer
Replace ns1.example.net with one of your actual authoritative nameservers.
An empty result from +short does not explain the cause. Run the command without +short to inspect the full response and status.
Then test the actual service:
www.A correct DNS answer does not prove that the destination website or mail server is working.
Check that you edited the authoritative DNS provider. Then compare its answer with the answer returned by your usual resolver.
If the authoritative server has the new value but a resolver has the old one, caching may explain the difference.
Check for:
www.Keep the old hosting available during a planned transition so visitors with cached answers can still use the site.
Review the MX records, email routing and mail-server hostname.
For example, if mail.example.com is a CNAME pointing to the website hostname, changing the website address can also change where that mail hostname resolves.
Check whether other records already exist at the same hostname. Also confirm that you are not trying to create a standard CNAME at the zone root.
SERVFAILAsk your DNS provider to investigate authoritative server availability and DNSSEC validation, especially after a nameserver migration.
Changing DNSSEC settings without coordinating the provider and registrar can make the problem harder to resolve.
Restore the previous values you recorded before editing, then verify the authoritative response.
Rollback does not instantly clear incorrect answers from every cache, so allow for the relevant TTL.
Avoid using Reset Zone as a troubleshooting shortcut. It can replace records needed by email and other services.
WHM users can manage available zones through DNS Functions → DNS Zone Manager, subject to their permissions. Reseller access is controlled by the administrator.
See the WHM DNS Zone Manager documentation.
Often, no. If you keep the same DNS provider, updating the relevant A, AAAA or CNAME record may be enough.
Changing nameservers moves DNS management and requires a complete, checked zone at the new provider.
Yes. Website and email services can be hosted separately.
Keep the required MX and mail-authentication records in place, and check whether any mail hostname depends on the website address.
The destination server may not be configured for your domain. A CDN cache, application setting or web-server configuration can also affect the result.
Once DNS resolves correctly, investigate the destination service rather than repeatedly changing records.
No. NS records identify authoritative nameservers. Glue records provide nameserver addresses where delegation requires them.
Do not change glue records simply because a website address record is incorrect.
DNS changes are not a ranking shortcut. The priority is to keep the website accessible and avoid downtime, broken URLs or certificate errors during a migration.
Contact DigitalBerg support with:
Share only the verification details needed for the task, and never send your account password.
Reviewed: 29 October 2026. Example hostnames and IP addresses are illustrative; use the settings supplied for your own service.

Addon Domain Checklist: 7 Essential Checks for Success
