How to compare Google Public DNS and Cloudflare DNS after a change

Quick answer for compare dns propagation resolvers

Query Google Public DNS and Cloudflare DNS for MX. When both show exclusive MailerZ and no leftover hosts, probe from another mailbox. That is compare dns propagation resolvers.

Guide: disagreement is TTL or wrong NS. Setup: save old set, cut exclusive, two views, then probe. Best practice: do not wait a week on a leftover you can delete now.

More views help. Two is the minimum.

Inbound history empty on all aliases is hop one, not fifty bad maps.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

compare dns propagation resolvers guide: the real decision

Waited a week with leftover Google still in 8.8.8.8.

Trusted only the registrar preview.

Probed during a split and recreated aliases.

Criteria: two public resolvers, exclusive MX, leftover gone, then unique subjects.

Technical mail flow for compare dns propagation resolvers

Resolvers cache MX. TTL is a hint. A leftover host still answers if you did not delete it.

After views agree, senders should hit MailerZ. Named aliases forward. Header From stays.

A city still on TTL is not dual MX you left on purpose.

Rollback republishes the saved set if the new hop is wrong.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP or POP, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA.

compare dns propagation resolvers setup

Write the expected MX hosts. Then query both resolvers. Then decide.

1. Save old MX. Cut exclusive MailerZ MX. Delete leftovers.
2. Query Google Public DNS and Cloudflare DNS.
3. If leftovers remain in both, delete — do not wait.
4. If they disagree, confirm answering NS and remaining TTL.
5. When they agree exclusive, probe from another mailbox.
6. Do not recreate aliases because one resolver is stale.
7. Recheck after a nameserver clone.
8. Do not self-send as the only view.

Failure modes and proof

Propagation as religion.

One resolver only.

Leftover called TTL.

Self-send.

Probed the whole sheet during a split.

MailerZ workflow and product boundary

Related: docs, tools, troubleshooting, migration planner.

Tools exist so you do not guess. History shows hops this layer saw.

Related pages: docs, DNS and MX tools, troubleshooting, and migration planner.

compare dns propagation resolvers best practice

Waiting a week on leftover MX costs customers, not resolver fees. Confirm hop /pricing. No inbox SLA while you wait.

Domain Connect helpers — nofollow — can change what resolvers see.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

GoDaddy mistakes are the panel. This is the lookup.

Authoritative NS versus registrar is a sibling topic.

Lower TTL before a planned cut if you can wait a day.

Agencies: two views per zone.

SOC 2 is still no.

14-day hops will not show leftover misses.

RFC 5321 is transport after MX resolves.

Do not invent a MailerZ resolver.

Deeper field notes for compare dns propagation resolvers

Why two views beat one green panel

Compare dns propagation resolvers because registrar previews cache and lie. Google Public DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) are two public caches operators actually hit. If both show exclusive MailerZ MX, hop one is visible to a useful slice of the internet. If either shows leftover Google, you are not done. Delete the leftover. Do not wait a week. TTL does not delete a record you left published.

Disagreement after a clean exclusive publish is remaining TTL or you edited NS that do not answer. Confirm authoritative nameservers. Lower TTL before a planned cut if you can wait a day. After the cut, raise TTL again. Lowering TTL does not fix a leftover.

When to probe

After views agree. Unique subject. Other mailbox. History. Dest including spam. Probing during a split recreates aliases that were never the bug. Fifty empty history rows are one leftover, not fifty maps.

Tools on /tools exist so you do not guess. Delivery recovery shows hops this layer stored. A leftover miss is not there. Related: docs, troubleshooting, migration planner.

Agencies

Two views per zone after every cut and after every nameserver clone. A template that restores leftovers will show up in 8.8.8.8 tomorrow. The GoDaddy article is the panel. This is the lookup.

A complete worked story

Cloudflare was clean. Google Public DNS was not.

They cut MX and checked 1.1.1.1. Clean. Customers still vanished. 8.8.8.8 still had Google. TTL was four hours, not four days. They waited the four hours, confirmed both views, probed, and stopped recreating aliases. Compare dns propagation resolvers was the missing step, not a new map.

Operator brief

A longer operator brief for compare dns propagation resolvers

Teams that bookmark How to Compare Google Public DNS and Cloudflare DNS After a Change usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about compare dns propagation resolvers as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is Mail Box portal webmail, not IMAP, not POP, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening compare dns propagation resolvers. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for how to compare google public dns and cloudflare dns after a change. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear compare dns propagation resolvers works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep compare dns propagation resolvers per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When How to Compare Google Public DNS and Cloudflare DNS After a Change is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how compare dns propagation resolvers stays a runbook instead of an incident.

A second worked pass for compare dns propagation resolvers: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a compare dns propagation resolvers mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Ten named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

What agreement between 8.8.8.8 and 1.1.1.1 actually proves

Compare DNS propagation resolvers after every MX cut because a registrar preview is not the internet. Google Public DNS at 8.8.8.8 and Cloudflare DNS at 1.1.1.1 are two caches operators actually hit. Agreement on exclusive MailerZ MX means a useful slice of the public path will see hop one. Agreement on a leftover means you are not done. Disagreement means remaining TTL or you edited nameservers that do not answer. It does not mean “wait a week and hope.”

Query the apex MX, not a hostname you invented. Query NS first if the cut also moved nameservers. A beautiful MailerZ set on GoDaddy DNS while Cloudflare still answers NS will never appear on 8.8.8.8. That is not slow propagation. That is the wrong desk. Print NS. Edit the panel that matches. Then compare the two public caches again.

Lower TTL a day before a planned cut if you can wait. After both views agree and a probe lands, raise TTL again. Lowering TTL does not remove a leftover host. It only makes a leftover show up faster in more caches. Delete first. Then wait. Then probe.

When a third view helps

If 8.8.8.8 and 1.1.1.1 agree and a customer still misses, add a third public view or a lookup from a phone off Wi-Fi. Corporate resolvers and some ISPs cache longer than 1.1.1.1. You still do not wait a week on a leftover you can print. You wait only when the leftover is gone and a cache has not expired. MailerZ history only stores hops that reached this layer. A leftover miss will not appear there. Do not open fifty empty recovery tickets for one leftover.

Probe only after views agree. Unique subject. Other mailbox. Check the destination including spam. Self-send from Gmail to the same Gmail can short-circuit and hide a split. Fifty green self-sends are not proof. One foreign probe after agreement is.

A cut that looked green in one cache

An agency cloned a client zone and restored an old Google MX from a template. The dashboard still showed MailerZ verify as done because the TXT had not moved. 1.1.1.1 still held exclusive MailerZ from the previous hour. 8.8.8.8 showed Google first. They called it propagation and sent invoices. Half the senders used a resolver that still saw MailerZ. Half did not. History looked random. The fix was delete the cloned leftover, flush the comparison, wait for both views, then send one new subject from a mailbox that was not the destination.

Tools on the site exist so you do not guess from a screenshot. Delivery recovery shows hops this layer stored. A leftover miss is not there. Related runbooks live on docs, troubleshooting, and the migration planner. This page is only the two-resolver check.

Agencies should run two views per zone after every cut and after every nameserver clone. A template that restores leftovers will show up in 8.8.8.8 tomorrow. The GoDaddy article is the panel. This article is the lookup. Do not merge them into one vague “DNS is weird” ticket.

How to query without guessing the UI

Use a public lookup that lets you pick the resolver, or query 8.8.8.8 and 1.1.1.1 from a machine you control. Ask for MX on the apex. Ask for NS if the cut included a nameserver move. Write the answers in the ticket as text. A screenshot of a registrar preview is not a resolver answer. A MailerZ dashboard green check is not a resolver answer.

If the two caches disagree, do not probe yet. Either a leftover is still published or TTL remains. Print the authoritative answer from the NS that actually own the zone. If the authority already shows exclusive MailerZ and one cache is stale, wait that cache’s remaining TTL. If the authority still shows a leftover, delete. Waiting never deletes.

After agreement, one foreign probe with a unique subject is the close. Check history and the dest store. If that probe is empty, you compared the wrong name — usually mail.example.com instead of the apex, or a parked zone. Compare again on the name customers type after the @. Then stop opening tabs. The next cut uses the same two resolvers. Confirm /pricing when you need send-as, not when you are still arguing caches.

What to type, and what a third resolver is for

Ask for MX on the domain people type after the @. Do not query a hostname you invented because a panel labeled it “mail.” If the cut also moved nameservers, ask for NS first. Write both answers in the ticket as text. A registrar preview is not a resolver. A dashboard check is not a resolver.

Google Public DNS and Cloudflare Resolver are enough for most cuts. Add Quad9 or a phone off Wi-Fi when those two agree and a customer still misses. Corporate resolvers and some ISPs cache longer than 1.1.1.1. You still do not wait a week on a leftover you can print. You wait only when the leftover is gone and a cache has not expired.

If the authoritative hosts already show exclusive MailerZ and one public cache is stale, wait that cache’s remaining TTL. If the authority still shows Google, Microsoft, or a registrar forwarder, delete. Waiting never deletes. MailerZ history only stores hops that reached this layer. A leftover miss will not appear there. Do not open fifty empty recovery tickets for one leftover host.

Save the old MX set as text before you delete it. If 8.8.8.8 and 1.1.1.1 still disagree after an hour, you can compare the authority to that saved set and see whether you edited the wrong panel. A nameserver move plus an MX edit in the same hour is how one cache looks green and the other still shows Google. Sequence the jobs: copy zone, flip NS, wait until NS agrees, then edit MX, then compare the two public caches, then probe.

Related lookup help lives on troubleshooting and the nameserver article on this blog. This page stays the two-resolver check. Do not merge it into a leftover-MX novel or a send-as setup. Confirm MailerZ pricing when inbound is boring and From must travel.

FAQ

What is the safest way to handle compare dns propagation resolvers?

After you publish exclusive MailerZ MX, look up MX on Google Public DNS and Cloudflare DNS. If both agree and leftovers are gone, probe from another mailbox. If leftovers remain, delete them. If views disagree, check nameservers and TTL. Do not wait a week on a leftover host.

Does this require a new mailbox?

No. MailerZ is Mail Box portal webmail (Inbox, Sent, New email). It is not IMAP or POP. Gmail or Outlook remains the store unless you separately buy a hosted mailbox product.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a verified mailbox. Branded replies need paid send-as plus Gmail Send mail as or a manual Outlook SMTP identity. Free has no send-as.

What DNS records are involved?

A verification TXT, one MailerZ MX set on the authoritative nameservers, leftover host MX removed, and SPF, DKIM, and DMARC if you also send as the domain.

What should I test before production?

Send a uniquely titled message from an unrelated provider into each named alias. Confirm Header From and delivery history. Do not email yourself from the same Gmail account.

Key takeaways

• Two resolvers.
• Exclusive expected.
• Leftover ≠ TTL.
• Wrong NS ≠ propagation.
• Probe after agree.
• Save old set.
• No self-send.
• No week on leftovers.

Conclusion and next action

Compare Google Public DNS and Cloudflare DNS after every MX change. When they agree on exclusive MailerZ, probe. When they show leftovers, delete. MailerZ cannot cache-bust a host you refused to remove.

Start free. Sign in if 8.8.8.8 still shows Google on a zone you cut.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.