May 12, 2023

How to speed up DNS propagation using Google Flush DNS, OpenDNS, CloudFlare DNS

Emergency procedure to minimize damage in an emergency DNS change.

Managing DNS settings is a delicate matter, which requires special attention for the correct setting of the Time To Live (TTL) of the respective records. The TTL is a fundamental parameter in controlling the frequency of updating DNS information. Too high a TTL value can mean a longer wait time when changes need to be propagated, such as redirecting a domain to a new IP address. Situations like these are common in the professional world, especially when inheriting a domain with a DNS TTL set to one day or more.

dig-TTL-DNS

We have some configuration of DNS TTLs talked about very exhaustively in this post, however, we believe it is appropriate to disclose emergency procedures to be shared also with our colleagues to avoid significant damage to the customers' business.

Let's imagine, for example, that the Customs and Monopolies Agency has mistakenly blocked a website. While waiting for the resolution of an appeal, which could take months, you might need to redirect the site to a .com domain on a foreign server, using a 301 redirect for all resources on the new domain. In this scenario, it may be necessary to point the old domain's IP to the new server, but this could take up to a week if the old domain's zone TTL is set to 604800 seconds (one week). How then can propagation be accelerated?

The reality is that most Internet users use the DNS of their connectivity providers (TIM, FastWeb, Vodafone, etc.), but a growing number of users, especially on smartphones, are starting to use Google nameservers, OpenDNS and CloudFlare DNS. These services cover about 20% of the entire DNS market. However, the main goal is to avoid a drop in SEO by Google, secondly, to try to lose as few potential customer users as possible.

For this reason, you can "force" flush the DNS cache for the most used DNS services.

What does it mean to flush the DNS cache?

DNS flush is a process that cleans and renews information saved (cached) by authoritative servers (i.e. managers and owners) regarding domains. This is particularly useful when a site changes server and consequently at least in theory also the IP address.

Google DNS, OpenDNS and CloudFlare DNS.

To force flush the DNS cache, you must and can use the functions provided by Google DNS, OpenDNS and CloudFlare DNS.

Google's public DNS, OpenDNS, and CloudFlare are widely used and respected domain name resolution services for their resilience and speed. These services act as translators between IP addresses and domain names, an essential process for surfing the Internet.

Google Public DNS is a free DNS service offered by Google, with the aim of making the web faster and more secure. Launched in 2009, Google Public DNS has earned a solid reputation for its reliability and speed. Google uses anycast technology to route DNS requests to the closest server, thereby reducing latency and ensuring fast response times.

OpenDNS is another very popular public DNS provider. In addition to offering fast and reliable DNS service, OpenDNS also offers security and content filtering features, making it a popular option for households and businesses. OpenDNS also uses anycast technology to ensure fast and reliable response to DNS requests.

Cloudflare DNS, also known as 1.1.1.1, is the latest addition to these services, launched in 2018. Despite its relative youth, CloudFlare DNS has quickly gained popularity due to its blazing speed. CloudFlare claims their DNS service is the fastest in the world, with global average response times significantly lower than other DNS providers. CloudFlare also uses anycast technology to optimize the speed and resiliency of its service.

Anycast technology is a key part of the speed and reliability of these DNS services. With anycast, DNS requests are directed to the closest server in terms of network latency, rather than in terms of physical distance. This means that DNS queries are usually resolved faster, improving browsing speed for the user. Resiliency is also improved, as if a server were to go offline, requests could simply be redirected to another server in the anycast network.

Google Public DNS, OpenDNS, and CloudFlare DNS are all excellent examples of how a public DNS service should work, offering speed, reliability, and additional features like security and content filtering. Their popularity is a testament to the quality of service they offer.

How to force DNS cache flush?

Google DNS: Google provides a public caching service which can be flushed by sending a special request to their server. Visit the Google Public DNS Flush Cache page (https://developers.google.com/speed/public-dns/cache) and enter your domain to begin the process.

Flush CacheGoogle DNS

OpenDNS: OpenDNS allows you to do a DNS flush through their refresh cache tool. Just go up https://cachecheck.opendns.com/ and enter the domain name.

After pressing “Check this domain”, you will see the “Refresh the cache” option which allows you to start the DNS flush process.

Cloudflare DNS: CloudFlare, also known as 1.1.1.1, offers a similar feature. You can access their cache purge tool through the link https://1.1.1.1/purge-cache/ which is presented in a way that is as spartan as it is efficient.

The Purge Cache tool of 1.1.1.1 allows you to refresh the DNS cache of 1.1.1.1 for domain names. To refresh the cache for a domain name, enter the name for the  domain  below, choose the  DNS record type  and then press  Purge Cache.

1.1.1.1 CloudFlare DNS Flush Cache

It is important to note that forcing a DNS flush can only accelerate DNS change propagation for those systems that have the ability to be forced such as those listed above. In this case the solution is an immediate solution within a minute. However, the complete propagation of a DNS change worldwide can take from a few hours to a few days, depending on the TTL set and the nature of the network. Flushing the DNS cache can help reduce this time, but it doesn't eliminate it entirely.

Also, flushing the DNS cache won't affect your site's SEO in a negative way, as long as the changes are handled properly. In particular, 301 redirects must be used carefully to ensure search engines understand that your site has moved to a new address. This way, your site will maintain its position in search results and continue to receive traffic.

Managing DNS settings is a key part of maintaining a website, and understanding how to speed up DNS propagation can make all the difference in critical situations. Remember that while DNS flushing can help reduce wait times, planning and managing your DNS settings correctly are the best tools to ensure your site remains accessible and visible, no matter the circumstances.

Do you have doubts? Don't know where to start? Contact us!

We have all the answers to your questions to help you make the right choice.

Chat with us

Chat directly with our presales support.

0256569681

Contact us by phone during office hours 9:30 - 19:30

Contact us online

Open a request directly in the contact area.

DISCLAIMER, Legal Notes and Copyright. RedHat, Inc. holds the rights to Red Hat®, RHEL®, RedHat Linux®, and CentOS®; AlmaLinux™ is a trademark of the AlmaLinux OS Foundation; Rocky Linux® is a registered trademark of the Rocky Linux Foundation; SUSE® is a registered trademark of SUSE LLC; Canonical Ltd. holds the rights to Ubuntu®; Software in the Public Interest, Inc. holds the rights to Debian®; Linus Torvalds holds the rights to Linux®; FreeBSD® is a registered trademark of The FreeBSD Foundation; NetBSD® is a registered trademark of The NetBSD Foundation; OpenBSD® is a registered trademark of Theo de Raadt; Oracle Corporation holds the rights to Oracle®, MySQL®, MyRocks®, VirtualBox®, and ZFS®; Percona® is a registered trademark of Percona LLC; MariaDB® is a registered trademark of MariaDB Corporation Ab; PostgreSQL® is a registered trademark of PostgreSQL Global Development Group; SQLite® is a registered trademark of Hipp, Wyrick & Company, Inc.; KeyDB® is a registered trademark of EQ Alpha Technology Ltd.; Typesense® is a registered trademark of Typesense Inc.; REDIS® is a registered trademark of Redis Labs Ltd; F5 Networks, Inc. owns the rights to NGINX® and NGINX Plus®; Varnish® is a registered trademark of Varnish Software AB; HAProxy® is a registered trademark of HAProxy Technologies LLC; Traefik® is a registered trademark of Traefik Labs; Envoy® is a registered trademark of CNCF; Adobe Inc. owns the rights to Magento®; PrestaShop® is a registered trademark of PrestaShop SA; OpenCart® is a registered trademark of OpenCart Limited; Automattic Inc. holds the rights to WordPress®, WooCommerce®, and JetPack®; Open Source Matters, Inc. owns the rights to Joomla®; Dries Buytaert owns the rights to Drupal®; Shopify® is a registered trademark of Shopify Inc.; BigCommerce® is a registered trademark of BigCommerce Pty. Ltd.; TYPO3® is a registered trademark of the TYPO3 Association; Ghost® is a registered trademark of the Ghost Foundation; Amazon Web Services, Inc. owns the rights to AWS® and Amazon SES®; Google LLC owns the rights to Google Cloud™, Chrome™, and Google Kubernetes Engine™; Alibaba Cloud® is a registered trademark of Alibaba Group Holding Limited; DigitalOcean® is a registered trademark of DigitalOcean, LLC; Linode® is a registered trademark of Linode, LLC; Vultr® is a registered trademark of The Constant Company, LLC; Akamai® is a registered trademark of Akamai Technologies, Inc.; Fastly® is a registered trademark of Fastly, Inc.; Let's Encrypt® is a registered trademark of the Internet Security Research Group; Microsoft Corporation owns the rights to Microsoft®, Azure®, Windows®, Office®, and Internet Explorer®; Mozilla Foundation owns the rights to Firefox®; Apache® is a registered trademark of The Apache Software Foundation; Apache Tomcat® is a registered trademark of The Apache Software Foundation; PHP® is a registered trademark of the PHP Group; Docker® is a registered trademark of Docker, Inc.; Kubernetes® is a registered trademark of The Linux Foundation; OpenShift® is a registered trademark of Red Hat, Inc.; Podman® is a registered trademark of Red Hat, Inc.; Proxmox® is a registered trademark of Proxmox Server Solutions GmbH; VMware® is a registered trademark of Broadcom Inc.; CloudFlare® is a registered trademark of Cloudflare, Inc.; NETSCOUT® is a registered trademark of NETSCOUT Systems Inc.; ElasticSearch®, LogStash®, and Kibana® are registered trademarks of Elastic NV; Grafana® is a registered trademark of Grafana Labs; Prometheus® is a registered trademark of The Linux Foundation; Zabbix® is a registered trademark of Zabbix LLC; Datadog® is a registered trademark of Datadog, Inc.; Ceph® is a registered trademark of Red Hat, Inc.; MinIO® is a registered trademark of MinIO, Inc.; Mailgun® is a registered trademark of Mailgun Technologies, Inc.; SendGrid® is a registered trademark of Twilio Inc.; Postmark® is a registered trademark of ActiveCampaign, LLC; cPanel®, LLC owns the rights to cPanel®; Plesk® is a registered trademark of Plesk International GmbH; Hetzner® is a registered trademark of Hetzner Online GmbH; OVHcloud® is a registered trademark of OVH Groupe SAS; Terraform® is a registered trademark of HashiCorp, Inc.; Ansible® is a registered trademark of Red Hat, Inc.; cURL® is a registered trademark of Daniel Stenberg; Facebook®, Inc. owns the rights to Facebook®, Messenger® and Instagram®. This site is not affiliated with, sponsored by, or otherwise associated with any of the above-mentioned entities and does not represent any of these entities in any way. All rights to the brands and product names mentioned are the property of their respective copyright holders. All other trademarks mentioned are the property of their respective registrants. MANAGED SERVER® is a European registered trademark of MANAGED SERVER SRL, with registered office in Via Flavio Gioia, 6, 62012 Civitanova Marche (MC), Italy and operational headquarters in Via Enzo Ferrari, 9, 62012 Civitanova Marche (MC), Italy.

JUST A MOMENT !

Have you ever wondered if your hosting sucks?

Find out now if your hosting provider is hurting you with a slow website worthy of 1990! Instant results.

Close the CTA
Back to top