Why one address can support several services
A business domain can be used for a website, email, verification and other services. DNS, the Domain Name System, is one part of how names are directed to those services. Changing where the website points does not automatically mean that the email provider should change too. That distinction matters when a redesign or hosting move is being planned.
You do not need to become a network engineer to protect the handover. You do need a current record of the providers involved, who has access and what must keep working. If you are unsure what a record does, ask the responsible provider before deleting or replacing it; an apparently unfamiliar entry can support a live service.
Identify who controls each part
List the registrar, the service hosting the authoritative DNS zone, the website host and the email provider. These may all be the same company, or each may be different. Also note any service used for marketing email, forms or domain verification. The company that sends a renewal invoice is not always the one currently managing the DNS records.
Sign in through the provider’s normal route to confirm access, and establish a responsible person for the change. Do not put passwords, recovery codes or secret keys in a public document or send them in ordinary email. Use delegated access or an appropriate secure sharing method where supported.
Read the common record types carefully
An A record can associate a name with an IPv4 address, while an AAAA record is used for IPv6. A CNAME makes a name an alias of another name, subject to DNS rules and the provider’s interface. MX records identify mail servers for a domain. TXT records can carry verification and email-authentication information, among other uses.
Your host should supply the exact records it needs; copy them carefully rather than adapting an example from a guide. DNS interfaces vary in whether they add the domain name automatically. Check the provider’s instructions for the host field and trailing dot, and avoid entering the domain twice. A record type that works for one setup may not be suitable for another.
Keep each domain service accounted for
- RegistrarRegistration and renewal
- DNS hostNames and service records
- Website hostWebsite files and delivery
- Email providerMailboxes and mail routing
Protect email and verification records
Before changing website records, document the existing mail configuration, including MX records and relevant TXT or CNAME entries supplied by the mail provider. Records such as SPF, DKIM and DMARC serve different email-authentication purposes and should be managed according to the provider’s actual instructions. Do not assume that an MX record alone is the whole email setup.
Some third-party services use TXT records to verify ownership. Keep a note of which service requested each record and why. Removing a verification record or an authentication record can have consequences even if the website still opens. If you are replacing an email provider as well, plan and test that as a separate migration.
Prepare a change plan
Export or securely record the current zone before making an agreed change, including names, types, values and time-to-live settings. This is a reference for recovery, not a guarantee that a simple reversal will solve every problem. Confirm the new website is ready and protected with the appropriate HTTPS certificate, and identify someone who can help if verification stalls.
Write down the exact records to add, edit or remove and the reason for each. Check whether the change applies to the bare domain, a www subdomain or both. If the host gives a verification record, allow time to complete it. Avoid making unrelated changes during the same window, so an issue is easier to investigate.
Check the website and mail after the change
DNS changes can take time to be observed by different resolvers, so people may temporarily see different results. Check the intended website address and any www version, certificate and important pages. Follow the provider’s status information rather than assuming an instant change means every network now sees the same records.
With the account owner’s agreement, send a small test email between appropriate inboxes and confirm both sending and receiving where relevant. Test an enquiry form separately because its delivery may use another provider. If something fails, document the time and symptoms and contact the relevant provider before changing additional records.
An illustrative move for a local business
Imagine a Hertfordshire consultant who keeps email with one provider but moves the website to another. The new host asks for website and ownership-verification records. The consultant first records the existing zone and confirms which MX and authentication entries belong to the mail provider.
After an agreed change, the consultant checks both versions of the website and sends a test email with consent. If verification is pending, the consultant follows the host’s instructions and checks the record before assuming that unrelated mail entries should be removed. The example shows a process; exact records vary by setup.
Keep a small record for the next person
Document the registrar, DNS host, website host, email provider, renewal owner and support contacts. Record the current purpose of each important record without exposing credentials. Give the business a way to access that record independently of the designer who completed the project.
Before the next supplier makes a change, compare the plan with that inventory and ask what will happen to email, verification and existing addresses. Where a change may affect business-critical services, arrange a suitable window and a recovery contact. Small checks before a move are usually easier than diagnosing several simultaneous changes afterwards.
A simple change-control note
Before the agreed change, write a two-column note describing the current record and the exact replacement supplied by the provider. Include the full hostname and record type so a colleague can distinguish the bare domain from www or a verification subdomain. Keep the previous values and the provider’s support contact in a protected project record. Do not publish records containing secret tokens in a public handover document.
Afterwards, note when the change was made, what the host reports and which tests were completed. A time-to-live value influences how long a resolver may cache an answer, but different systems can update at different times and a change is not guaranteed to be seen everywhere immediately. Avoid repeated unplanned edits while checking. If email or the website fails, explain which service is affected and ask the appropriate provider to review the recorded changes.
