Before you change DNS
To change domain nameservers, first confirm where the domain's DNS is actually managed. The registrar and DNS provider can be different companies.
Take a screenshot or export the current zone. Do not delete MX records used for email, and do not replace records that belong to a service you still use.
- Domain login
- The exact value supplied by your hosting provider
- A backup of existing DNS records
- Access to the destination project
Steps to change domain nameservers
Open the active DNS provider, find the domain's record list, and compare each required hostname with the values shown by your hosting provider.
Make one change at a time so you can identify which update fixed or caused the issue.
- 01
Confirm the hostname
Decide whether you are connecting the root, www, or another subdomain.
- 02
Copy the exact target
Copy the value from the current hosting dashboard; do not guess or include https:// in a DNS value.
- 03
Save and verify
Return to the destination service and use its verification or refresh control.
TYPE NAME VALUE
A @ <IP shown by your hosting provider>
CNAME www <target shown by your hosting provider>
TXT @ <verification value when requested>Propagation and verification
DNS answers are cached. A new record may work on one network before it works on another, which does not necessarily mean the setup is broken.
Check the exact hostname with a public DNS lookup. If the expected value appears, allow the hosting platform time to verify it and issue HTTPS.
Finish without breaking email or redirects
Test the root domain, www version, and any important subdomains. Send a test email if the domain uses custom email. Then choose one canonical website address and redirect the alternate version.
Keep the final DNS values in your project notes. That small step makes future migrations much easier.
Common mistakes to avoid
Most problems come from a small set of preventable choices. Check these before assuming the platform is broken.
- Changing several DNS records at once, which makes the real cause difficult to identify.
- Copying a value from an old tutorial instead of the current provider dashboard.
- Testing only the happy path and forgetting mobile, private browsing, or a failed request.
- Removing a working configuration without saving a screenshot or rollback note.
Troubleshooting
The change is not visible
Check the authoritative nameservers, query the exact hostname, and allow cached DNS answers time to expire.
The dashboard says configuration is invalid
Compare the type, name, and value character by character. Remove protocols such as https:// from fields that expect only a hostname.
It works on desktop but not mobile
Test on a real phone, check touch targets and viewport behavior, and look for scripts that fail on slower connections.
Frequently asked questions
How long does change domain nameservers take?
The edit itself usually takes a few minutes. DNS propagation and HTTPS verification may take longer, sometimes up to 24–72 hours.
Can I undo the change?
Usually, yes—if you record the original value first. For a live website, keep a backup or previous deployment available before you start.
When should I ask a developer for help?
Ask for help when the change affects payments, accounts, email, customer data, or a live domain you cannot safely take offline.
Useful official references
Provider dashboards change, so use these official references to confirm labels and values before editing a live setup.
About the author
Mujtaba Muneer
I’m an independent web developer with four years of experience building responsive websites, web applications, and API integrations. I write these guides to make technical decisions feel manageable.