Skip to main content

Melbourne Marketing Brief / #064 / ANALYSIS

Website move: keep business email working

Published by · · AI-assisted research and writing

16 November 2026 · ANALYSIS · EXISTING DNS AND EMAIL GUIDANCE

A website handover needs more than a homepage check. If the move also changes who manages the domain’s DNS records, business email needs its own review. Even with incoming mail preserved, the website’s enquiry notifications may use a different sending service from the office mailbox. Treat those as separate acceptance checks.

This is original practical analysis of existing documentation, checked on 16 November 2026. Cloudflare’s full-setup guide displays an update date of 29 July 2026. Google’s MX and SPF guides display 10 November 2026. These are documentation update dates, not new announcements today; the sources do not provide original publication dates.

Research and writing use AI assistance. No customer DNS zone, mailbox, website enquiry, email notification or provider account was inspected, changed or tested. Examples are hypothetical, not client incidents, measured outcomes or personal testing by Ajay. Google Workspace examples apply to that product; other mail providers require their own records and guidance.

01 / THE CHANGE SCOPE

A new website and a new DNS provider are different changes

Existing Cloudflare guidance · Updated 29 July 2026 · Checked 16 November 2026

Source facts

Cloudflare’s full-setup guide warns that its DNS quick scan is not guaranteed to find every existing record. It tells operators to review website, subdomain and email records. It also says the exact email-record values depend on the email provider.

The guide describes website records such as A, AAAA or CNAME separately from email records. This is guidance for Cloudflare’s full DNS setup, not a requirement that every website move change nameservers or move its mail service.

Cloudflare DNS: Set up a primary zone (Full setup)

Publication date not provided by the source. Source checked 16 November 2026.

Who this affects

Australian service-business owners whose website provider proposes a domain or DNS change. Ask which service is moving: the website, DNS management, email hosting or some combination. A business with no planned change can keep this as a handover reference rather than alter a working system.

Our analysis: what it means for your business

Our analysis: “the domain is connected” is too broad to be a useful handover result. The website can resolve correctly while a separate mail dependency is missing or different. The owner needs a clear change list and an authorised person responsible for the services that should continue working.

Hypothetical example: a plumbing business keeps its existing office mailboxes but moves its website. The new website provider also proposes changing nameservers. Before that change, the website and mail administrators agree which existing records must remain and which website records need replacing. A completed import is checked against the required records; it is not treated as a complete inventory by itself. No business migration was examined here.

Our recommendation: request a private record inventory and a written change scope before the move. Keep the DNS, mailbox and website owners identified, even if one provider fills several roles. If only website records need changing, ask why a wider nameserver change is proposed. Have the responsible provider plan validation and recovery; do not paste generic record values over the existing setup.

What to do next

  1. Confirm whether the proposal changes website records, authoritative DNS, email hosting or more than one service.
  2. Have the authorised providers compare the required records and agree who validates and recovers each service.

02 / INCOMING MAIL

Preserve the mailbox destination before replacing records

Existing Google Workspace guidance · Updated 10 November 2026 · Checked 16 November 2026

Source facts

Google explains that MX records tell the sending system where to deliver mail for a domain. Its Workspace setup guide still supports the legacy MX values beginning with aspmx and says working email using those records needs no change.

The same guide provides a newer single-record setup and warns that new MX records can take up to 72 hours to be recognised. That is a documented possible recognition period, not evidence that waiting will fix an incorrect configuration.

Google Workspace Help: Set up MX records for Google Workspace

Publication date not provided by the source. Source checked 16 November 2026.

Who this affects

Businesses keeping Google Workspace mail during a website or DNS move. Other mail services need their own provider’s values; do not copy Google’s setup into an unrelated mailbox service. A working legacy Workspace configuration does not need replacement merely because a newer example exists.

Our analysis: what it means for your business

Our analysis: confirming the destination of incoming mail is a separate task from opening the website or sending a message out of a mailbox. The business needs evidence that an enquiry addressed to its normal public email address reaches the intended inbox. That check should use an authorised test and have a named person confirm receipt.

Hypothetical example: a cleaning business can send quotes from the office mailbox after a website move. That does not establish that a new customer’s email to the business will arrive. The handover includes an approved incoming-mail check from an external address and a check of the intended mailbox or shared-inbox destination. No email was sent for this edition.

Our recommendation: preserve the existing intended mail service unless a separate mail migration is part of the agreed scope. Have the mail administrator compare the published MX records with that provider’s requirements. If mail fails, investigate the configuration and available delivery evidence rather than treating a propagation estimate as a diagnosis. A correct DNS lookup alone does not establish successful mailbox delivery.

What to do next

  1. Record which provider should receive incoming mail and have the authorised administrator verify its required MX records.
  2. Plan an approved incoming-mail check with actual receipt confirmation, separately from website and outgoing-mail checks.

03 / OUTGOING NOTIFICATIONS

The office mailbox and the website may send differently

Existing Google SPF guidance · Updated 10 November 2026 · Checked 16 November 2026

Source facts

Google describes SPF as a DNS TXT record listing authorised servers that send for a domain. It instructs administrators to identify all senders, including web servers, contact forms and third-party services, before determining that record.

Google also advises reviewing SPF when a new mail server or third-party sender is introduced. This concerns outgoing sender authentication; it does not establish that an incoming MX route or every website notification is working.

Google Workspace Help: Set up SPF

Publication date not provided by the source. Source checked 16 November 2026.

Who this affects

Businesses whose new website sends enquiry alerts, confirmations or other messages using their domain. If a separate existing service still sends those messages, establish that fact before changing authentication. This is not a recommendation to replace the mail provider or activate a newsletter.

Our analysis: what it means for your business

Our analysis: two systems can use the same business name while sending through different infrastructure. The office mailbox may work while the website’s notification path needs a separate configuration review. First establish whether the move changes the sender at all, then use the actual sender’s requirements.

Hypothetical example: a consultant’s office email stays with Google Workspace, but the rebuilt website uses a separate service for enquiry notifications. A Workspace-only example SPF record is not a substitute for identifying that actual sending arrangement. The authorised provider reviews the existing sender list and any other authentication requirements, then checks the approved website enquiry path. No form or notification was submitted here.

Our recommendation: make a small sender list covering office mail, website alerts and other authorised business systems. Ask the mail or sending-service administrator to review the necessary authentication before any record change. Validate the actual approved website-to-inbox path as well as mailbox sending. Authentication is one part of delivery; it does not guarantee inbox placement, prove a customer enquiry was accepted or confirm that a staff member replied.

What to do next

  1. Identify whether the website move changes the actual outgoing notification service and who owns its configuration.
  2. Have the authorised provider review sender authentication and plan an approved end-to-end enquiry-notification check.

ANALYSIS / BUSINESS CONTEXT

Where to spend your attention today

Our handover recommendation is three separate results: the website and its intended links work; approved incoming mail reaches the right destination; and the actual outgoing enquiry-notification path is verified. A single “website live” screenshot cannot establish all three. Keep the evidence and responsible person for each result together, so a failure can be traced to a specific service rather than prompting unrelated DNS changes.

Commercial context: Ajay Dabhi sells website, local SEO, advertising and automation services for Australian service businesses. The invitation below is separate from this analysis. Your existing authorised website and email providers may be able to complete the review. Digital services are Australia-wide; on-site visits are available in Melbourne. No customer records were changed, messages sent or Growthcenter integration tested.

Practical checks

  1. Agree the exact DNS and hosting scope before the website move.
  2. Keep incoming mailbox routing and outgoing sender authentication separate.
  3. Require approved checks of the real enquiry path rather than a homepage-only handover.

These checks are recommendations, not additional requirements announced by the platform. The appropriate work depends on your actual configuration.

Publisher and editorial information

Ajay Dabhi publishes this report and also sells marketing and automation services. The commercial invitation above is separate from the sourced reporting. No client account test or direct interview is claimed in this report.

Research and writing use AI assistance. Original documents are linked so readers can check the facts. Read our ownership, sourcing and corrections policy or report a correction to Ajay.

All Melbourne Marketing Brief editions →