A new site often requires DNS changes. Email depends on records that may live in the same zone as the website, so replacing the zone without inventory can interrupt mail. Treat the cutover as a change to a shared business system.
Check the real path
- Record the current DNS zone, provider logins, and every mail-related record before editing anything.
- Confirm whether the launch requires an A, CNAME, nameserver, or other change and which records should remain.
- Schedule the cutover with a named owner and a rollback plan; account for DNS propagation.
- Afterward, send and receive from external addresses and check mail authentication and website forms.
Decide what to change
Changing a web record does not inherently change mail, but changing nameservers or replacing the whole zone can. Keep the mail provider involved when records or routing are unclear.
Put it in the project brief
Before paying for a fix, ask the provider to name the affected page or workflow, the change they will make, how they will test it, and which dependencies or exclusions could change the estimate. Keep the baseline and the completed test so both sides can see what improved.
How ARCHV can help
ARCHV can coordinate agreed launch checks. Mail administration and DNS changes should be assigned explicitly to the party with account access. Share the current page and the problem through ARCHV's website estimate form. If you are an agency seeking delivery support, see the partner route.