Quick answer
Before moving a website while email stays elsewhere, export the current DNS records and record who owns each one and what depends on it. Leave mail and verification records alone unless you understand them, agree changes with whoever makes them, test email afterwards and name a rollback owner.
- Keep an unedited copy of the original records so you can restore them if something breaks.
- Verify by sending and receiving test emails after the change, because web and mail records often sit with different providers.
- If a record’s purpose is unknown, ask the provider and leave it alone until you have an answer.
Moving a website while email stays elsewhere requires care with DNS. This article helps plan changes by recording ownership, dependencies and rollback, without giving destructive instructions. It is written for business owners changing providers and ends with the decision, owner and next step to record.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
Situation. A website moves providers while business email must remain with its existing supplier.
What happens. A business moves its website to a new host while email stays with a separate provider. It exports the current DNS records, marks which ones the email depends on, agrees the changes with whoever performs them and arranges a test after the change and a rollback owner if mail stops.
Background
DNS is a set of published records that tell the internet where a name points. Websites and email commonly use different records, often managed by different providers, which is why a change meant for one can break the other. A web address record directs visitors to a host. Mail routing records direct email to a mail provider. Verification and authentication records support email trust and service ownership checks. Before any change, list every record, who put it there and what depends on it. Keep an unedited copy so you can restore it. Exact record syntax and timing vary by provider, so use your providers’ documentation for the actual edit.
Record ownership
List every DNS record and who owns each, by exporting from the current provider where possible. Use the record and current owner fields. You cannot plan a change safely if you do not know what exists.
Dependencies
Identify dependencies such as email and verification records and mark them clearly. Use the dependency field. Do not delete or alter records you do not understand. Ask the provider what each one does.
Change and rollback coordination
Agree verification and rollback with whoever makes the change. Use the proposed change, verification and rollback owner fields. Verification should include sending and receiving test emails. Keep a copy of the original records.
DNS change request template
Use this at the point described above. The workflow owner completes it and a named reviewer checks it. A completed row shows that the information, owner and next step are recorded; it does not prove the outcome. Keep it somewhere the team can edit, and keep it free of passwords, tokens and real client records.
Blank copy
| Record | Current owner | Dependency | Proposed change | Verification | Rollback owner |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Record | Current owner | Dependency | Proposed change | Verification | Rollback owner |
|---|---|---|---|---|---|
| Mail routing record | Email provider | Email delivery | No change | Send and receive test mail | Provider contact |
Working through the completed row
The row marks the mail routing record as owned by the email provider, depended on for email delivery, left unchanged and verified by sending and receiving test mail, with the provider contact as rollback owner.
Common mistakes
- Deleting records you do not understand.
- Changing DNS without a copy of the originals.
- Skipping the email test.
Questions to settle before you rely on it
- Which provider owns each record?
- What depends on it?
- How would you undo a change?
How you know it is complete
The template is complete when each record has an owner, dependency, proposed change, verification and rollback owner. Record who reviewed it and the date.
Where you may not have the answer
A record’s purpose is unknown. Ask the provider and leave it alone until you have an answer. The handoff, not a guess, is the correct next step.
Your next action
Export the records with the current provider.
Ask Web Design Davao to review this workflow and scope the website or marketing support required. Secure web hosting arrangements are agreed individually; nothing here assumes a particular service, role or timing is already available.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Domains and hosting can be held in the client’s name or managed by Web Design Davao, depending on the client’s requirements. Either way, record who holds each login and who can recover it.
Frequently asked questions
Why can a website move break my email?
Websites and email use different DNS records, often managed by different providers, so a change meant for one can break the other. Mail routing records send email to the mail provider, so altering them while moving the site can stop mail.
What should I record before changing DNS?
List every record, its current owner, what depends on it, the proposed change, how you will verify it and who owns rollback. Export from the current provider where possible, because you cannot plan a change safely without knowing what exists.
What if I do not know what a DNS record does?
Do not delete or alter it. Ask the provider what it does and leave it alone until you have an answer. Records for email delivery and verification support email trust and service ownership checks, so changing them blindly is risky.