Why email needs DNS records
Mail delivery depends on public DNS—especially MX records that name your mail hosts, and TXT records for authentication (SPF and related). NextShopper shows Required DNS for each mailbox so you can copy the exact records the mail adapter expects. If those records are missing or pointed at an old host, messages bounce or land in spam even when the mailbox password is correct.
This guide explains how to read Required DNS and publish the records on the domain’s authoritative DNS.
Who this guide is for
- New email customers setting up a domain for the first time
- Anyone whose mail sends but does not receive (or the reverse)
- Domains using either NextShopper DNS or an external DNS host
Before you start
- Open Emails → the mailbox → Required DNS.
- Confirm who hosts DNS (NextShopper nameservers vs external).
- Remove conflicting old MX records that point elsewhere unless you intentionally split services.
- Allow time for TTL after publishing.
Step-by-step: publish required records on NextShopper DNS
- Copy each required MX and TXT (and any others shown) from Required DNS.
- Open the domain → DNS records.
- Add record for each required entry with matching Type, Name, Value, and Priority for MX.
- Save until the set matches the Required DNS list.
- Wait for propagation, then send test messages to and from an external address (Gmail, etc.).
Step-by-step: publish on external DNS
- Keep nameservers at the external host.
- Enter the same Required DNS values in that provider’s DNS UI.
- Avoid creating the records only in NextShopper’s DNS tab if NS do not point here—they will not be authoritative.
What happens next / how to verify success
- External mail testers / dig show the new MX/TXT.
- Messages arrive in the mailbox.
- Sending is less likely to soft-fail SPF once TXT is correct (full DKIM/DMARC may include extra records when listed).
Common problems
| Problem | What to try |
|---|---|
| Still receiving on old host | Remove old MX; wait for TTL |
| SPF fail | Ensure TXT matches Required DNS; avoid multiple conflicting SPF strings—merge carefully |
| Records saved locally but ignored | Nameservers not on this zone—fix NS or edit external DNS |
| MX priority confusion | Lower numbers are higher priority; copy exactly |
| Domain suspended | Resolve FOA/billing first |
Frequently asked questions
Is Required DNS the same for every domain?
Values depend on the mail adapter and domain—always copy from your mailbox panel.
Do I need an A record for mail?
Follow Required DNS. Web A records are separate from MX.
Can I use Cloudflare or another DNS?
Yes—publish the same records there.
Will enabling DNSSEC break email?
Only if DNSSEC is misconfigured globally; fix DNSSEC separately if resolution fails.
Related guides
- How to view your mailboxes
- How to add, edit, or delete DNS records
- How to change domain nameservers
- How to change a mailbox password
Still need help?
Open a support ticket or Contact with the mailbox address and a screenshot/list of the Required DNS lines you published.