A browser website cannot directly flush your computer DNS. This tool checks public resolvers safely.
Inbuilt DNS resolver flush
Flush the Cloudflare 1.1.1.1 public resolver cache directly from this app for example.com A.
This flushes Cloudflare 1.1.1.1 resolver cache only. Google Public DNS uses a reCAPTCHA-protected browser form, not a public server-to-server API. This does not flush your computer, browser, router, ISP, or OS DNS cache.
Local DNS flush guide
Copy the right command for your device. Browsers cannot run these system commands automatically.
Windows
Run Command Prompt as Administrator
ipconfig /flushdnsmacOS
Run in Terminal, password may be required
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderLinux systemd
Modern systemd-resolved installs
sudo resolvectl flush-cachesLinux older
Older systemd-resolve installs
sudo systemd-resolve --flush-cachesLinux nscd
If Name Service Cache Daemon is installed
sudo service nscd restartLinux dnsmasq
If dnsmasq is used locally or on a router
sudo service dnsmasq restartChrome
Open this URL, then click Clear host cache
chrome://net-internals/#dnsEdge
Open this URL, then click Clear host cache
edge://net-internals/#dnsFirefox
Open this URL, then click Clear DNS Cache
about:networking#dnsRouter
Restart router DNS cache if your network still resolves old records
Restart router or reconnect WAN after saving DNS changesAfter flushing local DNS, close and reopen the browser tab, then re-check NS and A records. If the domain just changed nameservers, old delegation can still remain cached until resolver or TLD TTL expires.
Live DNS propagation map
Actual Google and Cloudflare DNS checks from regional Vercel functions.
Locations
18
Resolved
--
Partial/Error
--
Avg time
--
Washington, D.C.
United States - A - Standby - iad1
San Francisco
United States - A - Standby - sfo1
Portland
United States - A - Standby - pdx1
Montreal
Canada - A - Standby - yul1
Sao Paulo
Brazil - A - Standby - gru1
London
United Kingdom - A - Standby - lhr1
Dublin
Ireland - A - Standby - dub1
Frankfurt
Germany - A - Standby - fra1
Paris
France - A - Standby - cdg1
Stockholm
Sweden - A - Standby - arn1
Dubai
United Arab Emirates - A - Standby - dxb1
Mumbai
India - A - Standby - bom1
Singapore
Singapore - A - Standby - sin1
Hong Kong
Hong Kong - A - Standby - hkg1
Seoul
South Korea - A - Standby - icn1
Tokyo
Japan - A - Standby - hnd1
Osaka
Japan - A - Standby - kix1
Sydney
Australia - A - Standby - syd1
Propagation details
DNSChecker-style resolver breakdown for every available probe location.
| Location | Region | Google DNS | Cloudflare DNS | Min TTL | Status |
|---|---|---|---|---|---|
Washington, D.C. United States | iad1 North America | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
San Francisco United States | sfo1 North America | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Portland United States | pdx1 North America | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Montreal Canada | yul1 North America | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Sao Paulo Brazil | gru1 South America | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
London United Kingdom | lhr1 Europe | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Dublin Ireland | dub1 Europe | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Frankfurt Germany | fra1 Europe | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Paris France | cdg1 Europe | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Stockholm Sweden | arn1 Europe | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Dubai United Arab Emirates | dxb1 Middle East | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Mumbai India | bom1 Asia | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Singapore Singapore | sin1 Asia | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Hong Kong Hong Kong | hkg1 Asia | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Seoul South Korea | icn1 Asia | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Tokyo Japan | hnd1 Asia | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Osaka Japan | kix1 Asia | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Sydney Australia | syd1 Oceania | Waiting No probe response yet | Waiting No probe response yet | -- | Standby |
Production note: this lists every Vercel Function region currently exposed by the app. On Vercel, each endpoint requests its preferred region before querying free DNS-over-HTTPS resolvers. In local development, probes run from your machine.