By Touchbase Technologies · Published

Connect a website domain while preserving business email

Connecting a website usually involves changing the records that direct visitors to the hosting service. Your business email may use other records under the same domain. Before editing anything, identify the existing services, save the current configuration and confirm exactly which website records the new provider requires.

This is a preparation and verification checklist. The example names and worksheet below are illustrative, not DNS values to paste into a live account. Use the records supplied by your own hosting and email providers, and have the person responsible for your domain approve the change.

A flower-shop owner and web professional review website setup at a counter beside a mailbox representing the existing email service.

Identify the three services involved

Your domain registrar, DNS host and website host may be different companies. The registrar manages the domain registration. The DNS host serves the domain's DNS records. The website host serves the site. Your email service may be another provider again.

Write down which account controls each service and who within your business can access it. A website builder's domain screen may tell you what to add without being the place where you actually edit DNS. Use the authoritative DNS account for the domain rather than editing an inactive copy of the zone somewhere else.

GoDaddy's DNS management guide explains how DNS records connect domains to services. Follow the corresponding help for the provider that actually hosts your DNS. The relevant control may have a different name or format from the website host's instructions.

Save an inventory before making changes

Use the provider's supported export or a clear private record of the existing zone. Record the hostname, record type, destination, TTL and any provider-specific setting needed to restore the configuration. Include the date and the person who captured it.

Keep an owner for the change and an owner for verification. If someone else has already begun a migration, coordinate with them before adding another independent change. A useful change record explains the intended website address, the affected records and how the team will check the result.

ServiceInformation to capturePerson to confirm it
Domain registrationRegistrar and business account ownerDomain owner
Authoritative DNSDNS host and current zone inventoryDNS administrator
Existing websiteCurrent website records and intended replacementWebsite maintainer
Business emailCurrent provider and its required mail recordsEmail administrator
New websiteExact address and provider-supplied connection instructionsNew website owner

Do not share account passwords in the handoff document. Give collaborators access through supported account roles where possible. Keep the inventory available to the person who would need to restore an approved configuration.

Separate website records from mail records

Cloudflare's DNS record reference explains A/AAAA records, aliases such as CNAME, mail-routing MX records and TXT records. A website connection and an email setup use different purposes even when the names share a domain.

The same reference describes SPF, DKIM and DMARC email authentication records. Keep existing mail configuration in the inventory rather than treating it as disposable website setup. Cloudflare's email-record guidance is a useful provider-specific reference when Cloudflare hosts the zone.

For example, a fictional shop might want a new website at www.shop.example while continuing to use the same mailbox provider for messages addressed to the business domain. A website host may supply a CNAME for the www name and an ownership-verification record. That instruction does not, by itself, tell the owner to remove the domain's MX or email-authentication records.

A root-domain connection may use different instructions from a www subdomain. Some DNS providers offer special handling for apex aliases. Ask the website host and DNS provider for the supported setup rather than copying a subdomain example onto the root name.

Review the exact requested change

Read each row in the website provider's setup screen. Confirm the record type, the name field and the target value. Some dashboards want a relative name such as www; others show a full hostname. Check the DNS provider's format so you do not accidentally duplicate the domain name.

If a record already exists for the requested website name, identify what uses it before replacing it. Resolve the specific website-record conflict with the responsible owner. Do not clear the entire zone because one record conflicts with the new instructions.

Keep a nameserver migration separate from an individual record edit. If the chosen setup requires moving DNS hosting, plan that as a larger migration that carries all required services across. Simply recreating the website record at a new DNS host may leave email or other services missing.

Use a small approval worksheet

Before saving the change, ask another responsible person to read the proposed records against the provider's instructions. This suggested worksheet helps make the scope visible; it is not a configuration export.

CheckExample decision for the fictional shop
Website addressConnect the www subdomain named in the website dashboard
TargetCopy the exact hostname supplied for this site
Existing website recordConfirm which current entry is being replaced
Ownership verificationAdd only the requested record for the intended service
Mail settingsPreserve the current provider's MX and authentication records
DNS hostingKeep the existing DNS host unless a separate migration is approved
Verification ownerAssign someone to check the public website and business email
Recovery informationRetain the previous approved records and the reason for the change

If an instruction is unclear, pause and ask the provider for clarification. An incomplete or ambiguous setup is easier to resolve before several unrelated records have been changed.

Verify the website and email independently

After applying the approved website changes, use the provider's domain verification status and check the exact public address. Confirm that it shows the intended site, uses a valid HTTPS connection and handles the addresses you intend to advertise. A successful DNS verification is one milestone; the public website still needs checking.

If a browser reports a certificate problem, resolve it through the hosting provider rather than asking customers to bypass the warning. Check whether both the root and www addresses need configuration and which one should be the primary address.

Have the email owner verify the existing mail workflow separately. Using appropriate test accounts and permission, check that an inbound message reaches the intended mailbox and that a response can be sent. A visible website does not prove that email still works, and a successful email exchange does not prove that the website is ready.

DNS and certificate changes can take time to become visible across systems. Record what the authoritative configuration shows, what each verification tool reports and when you checked it. Avoid assuming every delay has the same cause or repeatedly changing values while earlier changes are still being evaluated.

Check the customer task before announcing the address

Open the site on a phone and follow the important public task. Check the contact information, inquiry form, product details or booking link that customers will use. If a test submission is appropriate, agree it with the form owner and label it clearly so nobody mistakes it for a real customer request.

For search discovery, review the intended public pages, internal links, canonical settings and sitemap with the website provider. A functioning domain is necessary for the customer experience, but it does not guarantee Google indexing or a search position. The SEO proposal checklist explains the difference between completed technical work and observed search outcomes.

Finish the handoff with the final website address, the records changed, verification results and the person responsible for future renewals and support. Keep the customer-inquiry handoff checklist beside the website setup so new requests reach a real owner after launch.

Keep the purchase and the configuration clear

This checklist applies regardless of which website platform you choose. If Touchbase is on your shortlist, review its current plans and allowances and the setup instructions provided for your particular site. Use your actual provider-supplied records; this article supplies no universal target hostname or IP address.

Check the public journey after the address connects

A correct-looking DNS record is only one part of the release. Open the intended public hostname while signed out and verify the actual business page, its main action and any external destination. Record whether you tested the root address, www or another subdomain; do not assume one result applies to every hostname.

Keep a short release note with the URL, observed result, responsible person and any unresolved difference. The website launch checklist helps review the visitor's task after connection. DNS verification alone does not demonstrate that a booking link, form destination or published revision works.

Questions before editing DNS

Should I delete existing records to start clean?

Inventory the services first and change only the approved entries. Existing records can support email, verification and other services that are not obvious from the website connection screen.

Does connecting www automatically configure the root domain?

Check the instructions for both addresses. They can require different records or provider-specific handling. Verify the public behavior you intend customers to use.

What if the website works but email fails?

Treat email as a separate verification failure. Give the email administrator the recorded changes and previous configuration, then use the mail provider's guidance to investigate. Do not keep altering unrelated website records without a diagnosis.

Prepared with AI assistance and checked against the sources linked in this guide.