You change the nameservers at your registrar, then you flip on Cloudflare Email Routing, and mail starts flowing. That is the story half the tutorials tell. It is also the reason so many people end up staring at a dashboard that says “not active” while their test messages bounce. The nameserver change is not instant, and Email Routing will not switch on until Cloudflare can actually see the delegation. Get the order wrong and you will spend an afternoon debugging a problem that only needed patience.
Why the nameserver switch does not take effect the moment you save it
When you edit nameservers at your registrar, you are not editing a live routing table. You are publishing a change to the parent zone, and that change has to propagate across resolvers that cache the old values. Until the TTL on the previous NS records expires and resolvers pick up the new ones, queries for your domain still land on the old servers. That window is usually minutes, but it can stretch to hours or longer depending on the registry and the previous TTL.
Cloudflare, meanwhile, is polling for the delegation. It checks the parent zone to confirm the nameservers now point at Cloudflare’s assigned pair. Only when that check succeeds does the zone move from Pending to Active. This is the step people skip. You can add a domain, copy the two nameservers, paste them at the registrar, and assume you are done. You are not done until the Cloudflare dashboard shows Active. Until then, Cloudflare is not authoritative for your DNS, and nothing you configure inside it, including mail records, will resolve for the outside world.
The skeptic’s version: “propagation” is a lazy word that hides a real dependency. The thing that matters is not how long DNS takes in the abstract. It is whether Cloudflare has confirmed the delegation. Treat Active status as your green light and ignore everything else.
The correct order for Cloudflare Email Routing setup
Do this in sequence. Skipping ahead is how people end up with MX records pointing at a zone that is not yet serving.
- Add your domain in the Cloudflare dashboard and note the two assigned nameservers.
- Remove the existing nameservers at your registrar and replace them with Cloudflare’s pair. Save the change.
- Wait. Watch the Cloudflare overview until the zone status reads Active. Do not touch email settings before this.
- Open Email Routing and add your destination addresses, then click the verification link sent to each mailbox.
- Let Cloudflare add the MX, SPF and DKIM records, or add them yourself if you have existing mail records you need to preserve.
- Create routing rules, including a catch-all if you want one, once the destination shows as verified.
The trap in step five is that Cloudflare wants to add MX, SPF and DKIM records to your zone. If you already run Google Workspace or Microsoft 365 on that domain, those records exist and Email Routing will either conflict or overwrite them. Email Routing is a receiver, not a mailbox provider. If your real mail lives in Gmail via Google Workspace, do not point the root MX at Cloudflare. Use Email Routing only on domains or subdomains where Cloudflare should be the final destination.
Destination addresses must be verified before rules activate. You add an address, Cloudflare sends a confirmation email, you click it, and the address flips to verified. An unverified destination silently does nothing, and a rule pointing at it will not deliver. This is the second most common “it doesn’t work” cause after enabling too early.
What to expect once Email Routing is live, and where it stops
Once the zone is Active and your rules exist, mail addressed to your domain hits Cloudflare’s MX, matches a routing rule, and is forwarded to the verified destination. A catch-all rule catches any address not matched by a more specific rule, which is handy for throwaway signups and role addresses like info@ or sales@. Each routing rule supports one destination address, so fanning a single inbox out to three people means three rules.
Know the ceilings before you design around them. Routing rules per domain are limited to 200, the maximum message size is 25 MiB, and anything larger is rejected rather than queued. Cloudflare Email Routing does not support sending or replying from the domain. It is inbound only. If you need outbound, that is a different product: Cloudflare Email Service groups Email Routing and outbound sending under one roof, and for programmatic mail, as explained at https://allmail.one/blog/cloudflare-email-forwarding/, you would look at Cloudflare Workers rather than the routing rules UI.
Forwarding to Gmail works cleanly as long as the destination is verified and your SPF and DKIM records are intact, since Gmail is stricter than it used to be about unauthenticated forwards. If messages land in spam, check that Cloudflare’s DKIM selector is present and that you did not leave a stale SPF record from a previous provider. A leftover include for an old host is a common culprit.
If you are migrating from another forwarder, keep the old MX records in place until the new zone is Active and a test message has landed in the destination inbox. There is no reason to create a mail gap just because the DNS change is technically ready.
Point the nameservers first, then wait for Active, then enable Email Routing and verify every destination before you build rules. Test with a single message to a known address before you add the catch-all, and check the routing log if it does not arrive. If you run real mailboxes elsewhere, keep Email Routing off the root and confine it to the domains or subdomains where Cloudflare should be the endpoint. The whole process is boring when you respect the order and maddening when you do not.