Get the exact DNS instructions from your host, identify where your authoritative DNS is managed and preserve existing email records. Change either the intended records or the nameserver delegation deliberately, not both by guesswork.
Know where DNS is managed
The company that registered the domain is not always the company serving its DNS records. Check the current nameserver delegation and the DNS dashboard it points to. A record changed in an inactive zone will not update the live domain.
Before making changes, export or record the existing zone. Pay particular attention to mail routing, sender authentication, subdomains and ownership-verification records. A website connection task should not accidentally disconnect business email.
Choose the connection method
One method is to leave DNS with its current provider and add the website records supplied by the host. Another is to delegate the domain to the host's nameservers. The correct choice depends on the host's instructions and which services you need to preserve.
Changing nameservers moves responsibility for the entire DNS zone. Recreate necessary records in the target zone before the switch. If DNSSEC is enabled, coordinate its delegation records with the DNS provider; mismatched settings can prevent resolution.
Understand common record types
| Record | Typical purpose | Check before editing |
|---|---|---|
| A | Points a name to an IPv4 address | Use the exact address given by your host |
| AAAA | Points a name to an IPv6 address | Remove stale entries only after confirming the intended setup |
| CNAME | Aliases a name to another hostname | Follow the DNS provider's rules, especially at the zone root |
| MX | Routes incoming email | Preserve the mailbox provider's values and priorities |
| TXT | Holds verification or policy information | Do not discard existing email authentication records |
This is a functional overview, not a set of values to paste into your domain. Never copy an example IP address from an unrelated tutorial as your destination.
Apply and verify the change
- Add the domain in the hosting account and obtain its current connection instructions.
- Prepare the destination site and preserve a recovery copy of the existing DNS zone.
- Update the relevant records or nameservers in the correct control panel.
- Check the main domain and the intended www hostname.
- Enable or issue the appropriate HTTPS certificate once validation can succeed.
- Test the website, inbound email, outbound email and important subdomains.
Troubleshoot methodically
DNS answers can remain cached, so two networks may temporarily see different results after a change. Rather than repeatedly editing records, first check the authoritative answer and the intended target. Then compare it with what the affected device receives.
If some visitors reach the old site, inspect both A and AAAA records and any CDN configuration. If only HTTPS fails, investigate certificate coverage and validation instead of immediately changing the website IP. If email fails, compare the MX and relevant TXT records with the mailbox provider's instructions.
Keep a rollback plan
Maintain the previous site for an appropriate validation window and record what you changed. Dynamic sites may need special handling to avoid splitting new orders or updates between environments. Decide which system is authoritative before allowing writes during a migration.
After the connection is stable, document the final DNS provider, hosting destination and certificate process. That small handover record makes the next migration or outage easier to investigate.
Common questions
How long do DNS changes take?
Caching and delegation behavior vary. Follow the provider's guidance, check the authoritative records and avoid a universal promise that every change completes within one fixed time.
Do I have to change my email provider?
No. Website hosting and email can stay separate. Preserve the correct mail records and test email after the change.
Sources & reference notes
Official sources consulted on 9 October 2026. Product details may change. Sources describe provider claims or technical documentation, not independent test results.
Independent educational hosting resources. Prepared with AI-assisted research and drafting; no individual expert credentials or firsthand testing are implied.
About the publication · Editorial standards · Suggest a correction