A storefront change should not casually replace the configuration that keeps business email working. Treat the domain as shared infrastructure even when the immediate task concerns only the shop.
Inventory the services before editing
List the website, email provider and any other applications using the domain. Ask the authorised operator to identify the records and provider settings supporting them. Do not infer that every unfamiliar entry is obsolete.
The inventory should contain record names and purposes, not account passwords or secret recovery information.
Ask for the smallest required change
Use the storefront host's exact instructions for the intended hostname. If the proposed action replaces nameservers or imports a whole zone, stop and account for every existing service first. A one-record connection and a zone migration are not the same task.
Do not follow an instruction for another merchant's domain just because the platform name is the same.
Keep a readable before-state
Retain an authorised export or record of the relevant configuration and who captured it. Record the email provider's current setup separately so a later issue can be compared with evidence rather than memory.
Protect that file appropriately. Some configuration details are public, but the surrounding account information may not be.
Test the services that must survive
Plan a website check and an authorised email send-and-receive check using appropriate business test accounts. Do not use a customer's inbox as a diagnostic tool.
A page loading successfully is not evidence that mail still works. Conversely, an email delay should be investigated without immediately reversing unrelated storefront changes.
Keep ownership clear after launch
Name who handles domain renewal, email-provider administration and hosting changes. If different people own those tasks, document the handoff so the next change is not made in isolation.
This article is a preservation checklist, not provider-specific DNS instructions. Ask the relevant providers to confirm their required records and use an authorised operator for changes. The domain and platform decision guides help separate the services you are buying before a low-cost website offer becomes an unexpected email migration.
Illustrative case to check
A hosting guide suggests changing nameservers, but the domain also carries the business mailbox. Treat that as a broader migration requiring the existing mail configuration, not as a routine storefront step. Ask whether a narrower connection is supported. If the broader change is necessary, include authorised mail checks and a complete preservation plan before any edit.
Examples are illustrative. Confirm current features, charges and suitability before making a business decision.
Explore this topic → · Find an oBizee setup guide · Ask about your store