Connecting business email: a DNS checklist
Email delivery depends on DNS records as well as mailbox setup. Copy the values assigned to your domain by the actual email provider; do not borrow example records from another account.
Record the current setup
Find where the authoritative DNS zone is managed and save the existing mail-related records. Identify every legitimate sender, including the mailbox service, newsletter tool and website forms. A nameserver change can affect all of them.
Apply the provider’s instructions
- MX: routes incoming mail to the intended service.
- SPF: identifies allowed sending infrastructure; reconcile existing senders rather than blindly adding conflicting records.
- DKIM: uses provider-issued signing configuration.
- DMARC: sets handling and reporting expectations based on authentication alignment.
Test before tightening policy
Send and receive test messages with an outside mailbox. Inspect the actual results and confirm that website and marketing mail still work. A strict rejection policy applied before legitimate senders are configured can disrupt delivery.
Make one documented change at a time and allow for cached DNS answers. If mail breaks, provide support with the domain, approximate time and a redacted error message. Never publish mailbox passwords, private keys or full customer messages in troubleshooting screenshots.
Your next step
Compare business-email plans. Confirm current availability, inclusions and billing terms before purchasing.