Choose where the mailbox or forwarding lives
Owning a domain does not create an inbox. A mailbox provider offers storage and sending capabilities under its own terms; a forwarding service sends incoming messages to another address and may not provide outbound mail. Decide what the business needs before changing DNS. Check current provider features and pricing rather than assuming hosting includes every email capability.
Use the provider’s exact receiving records
MX records direct incoming mail to the selected service. Verification records may also be needed to establish domain ownership. Use the values supplied for your account and preserve unrelated website records. If migrating from an existing provider, plan data transfer and cutover instead of adding a second set of mail records without understanding the resulting behaviour.
Plan authentication coherently
SPF, DKIM and DMARC serve different roles in sending-domain authentication and policy. Follow the chosen providers’ instructions and account for every authorised sender. Do not publish a second SPF policy record for the same name as a quick fix. DMARC policy changes should reflect verified alignment and monitoring; copying a strict policy blindly can disrupt legitimate mail.
Test actual conversations
Send an authorised test from another account, check receipt and spam handling, and reply from the intended business address. Test any website sending service separately because it may use a different domain or provider. Review delivery logs and authentication results where available. A visible address on the website is not proof that its inbox or reply path works.
Your practical checklist
- Choose mailbox versus forwarding deliberately
- Apply exact provider DNS values
- Coordinate authentication across authorised senders
- Test incoming mail, replies and website delivery
Working through a similar question?
We’re happy to help you find a practical starting point.
Talk to AMGK