Domains and DNS
Coordinate outbound-domain authentication from one workflow.
Use the Cloudflare-based setup path to coordinate nameserver delegation and prepare SPF, DKIM, and DMARC. Confirm the resulting records with independent DNS checks before sending.
Cloudflare-based setup·SPF, DKIM, and DMARC workflow·Visible nameserver status
Setup flow
One registrar change, then verify each stage.
Add an owned domain
Enter the root domain you control. MailSequence validates the format and prevents the same domain being claimed across customers.
Copy assigned nameservers
The workspace shows the expected nameservers for the provisioned DNS zone.
Update the registrar
Replace the current nameservers where the domain is registered, then allow time for global propagation.
Verify delegation
Refresh the domain status to compare detected nameservers with the expected pair.
Prepare authentication records
The Cloudflare-based path coordinates SPF, DKIM, and DMARC setup after delegation.
Verify before sending
Use independent DNS checks to confirm the published records. Product status should be treated as workflow state until live DNS-record validation is fully verified.
What the workflow covers
The records that establish sending identity.
Authentication is table stakes for business email. MailSequence coordinates the core-record setup path in the delegated Cloudflare zone; operators should still verify the published result before sending.
- SPF policy for authorized sending infrastructure
- DKIM public key under the MailSequence selector
- DMARC policy and aggregate-report address
- Nameserver and setup-state visibility
Control and responsibility
Automated setup still starts with a domain you control.
You retain registrar ownership
MailSequence needs nameserver delegation to manage the DNS zone. The domain remains registered to you, and you make the registrar-side change.
Authentication has clear limits
Correct records remove preventable configuration errors. Reputation, audience quality, message relevance, volume, and recipient behavior still determine outcomes.
FAQ
Frequently asked questions
Do I need to move my domain registration?
No. Keep the domain at your registrar. You update its nameservers to the values assigned during setup so MailSequence can manage the DNS zone.
Which DNS records are covered by the setup path?
The Cloudflare-based path covers SPF, DKIM, and DMARC after nameserver delegation. Confirm the final published values with independent DNS checks before sending.
Can I use my own Cloudflare account?
Organization-level Cloudflare connections are supported for teams that want the zone created in their own account. Otherwise, availability depends on the platform DNS configuration.
How long do nameserver changes take?
Propagation time is controlled by DNS caches and the registrar. Changes may appear quickly but can take up to 24–48 hours to propagate globally.
Should I use my company's primary domain for cold email?
Use an owned domain chosen for outbound and protect the reputation of business-critical mail. The right domain strategy depends on your brand, risk tolerance, and sending program.
Does correct DNS guarantee inbox placement?
No. SPF, DKIM, and DMARC authenticate sending identity; they do not override reputation, list quality, copy, volume, recipient behavior, or provider filtering.
Keep domain setup connected to campaign readiness.
Connect an owned domain, delegate its nameservers, prepare authentication records, and verify the published result.