6 ms·

Google and Cloudflare allow anybody to expire any record in their cache, handy to have to if you make a mistake that is affecting customers. Google's 8.8.8.8:

Google and Cloudflare allow anybody to expire any record in their cache, handy to have to if you make a mistake that is affecting customers. Google's 8.8.8.8: https://developers.google.com/speed/public-dns/cache https://developers.google.com/speed/public-dns/cache Cloudflare's 1.1.1.1: https://1.1.1.1/purge-cache/ https://1.1.1.1/purge-cache/

brycewray 5y ago
OpenDNS: https://cachecheck.opendns.com/ https://cachecheck.opendns.com/
Hamuko 5y ago
I tried using the 8.8.8.8 one for one domain, but sending emails from Gmail to that domain failed for hours, so it's not perfect. One would at least think that Gmail uses 8.8.8.8 for DNS.
- fragmede 5y ago
  Domains themselves don't use DNS servers in the same way your network connection needs DNS to work right. Did you try using 8.8.8.8 for your domain's nameservers? Because that's a misconfiguration - your domain's nameservers need to be configured to be authoritative for your domain - which Google's HonestDNS is not going to claim to be. (Even if you're using GCP.)
  - dwild 5y ago
    I think he meant he used the Flush Cache functionality of 8.8.8.8 but emails still failed on Gmail until their cache was invalidated (so Gmail probably is not using 8.8.8.8, or the flush cache doesn't actually works as intended).
    - lathiat 5y ago
      caches are hierachical. Even your local machine most of the time now with recent OS releases will cache records, then your home router or some other DNS server on your network will often cache things before then referring to your ISPs or Googles DNS server. Invalidating the cache at one doesn't invalidate the cache downstream of them if they already looked the record up recently. But it does mean that anyone who hadn't looked up the record will get the correct result straight away.
- BenjiWiebe 5y ago
  Was it failing at GMail before you flushed at 8.8.8.8? Because then you would have to wait while GMail's own cache expired, assuming they even use the public 8.8.8.8 service.
belter 5y ago
1) What if we purge 8.8.8.8 at 8.8.8.8 ? 2) What if we purge 1.1.1.1 at 1.1.1.1 ? 3) What if we purge both about the other at the same time? 4) What if we purge aaaaaaa! So much time...so many ideas...are they sure they will end up well?
- belter 5y ago
  I guess the downvotes are about 1 and 2 but ok, I meant dns.google and one.one.one.one
- Dylan16807 5y ago
  You purge domains, not IPs. And it's not like they need to hold on to any state to work. If you had access you could purge everything and have them start fresh from the root servers, and it would work fine. (As long as the load spike doesn't make it decide to do something dumb, of course.)
- kelnos 5y ago
  > 1) What if we purge 8.8.8.8 at 8.8.8.8 ? 8.8.8.8 isn't a DNS name, it's an IP address. There's nothing to purge.
  - belter 5y ago
    I realize that. Sorry...I meant to say dns.google from dns.google one.one.one.one from one.one.one.one
arantius 5y ago
FYI There's an easier-to-remember URL for Google: https://dns.google/cache https://dns.google/cache The URL above is the documentation of the feature, which happens to also embed it.

brycewray 5y ago

OpenDNS: https://cachecheck.opendns.com/ https://cachecheck.opendns.com/

Hamuko 5y ago

I tried using the 8.8.8.8 one for one domain, but sending emails from Gmail to that domain failed for hours, so it's not perfect. One would at least think that Gmail uses 8.8.8.8 for DNS.

fragmede 5y ago
Domains themselves don't use DNS servers in the same way your network connection needs DNS to work right. Did you try using 8.8.8.8 for your domain's nameservers? Because that's a misconfiguration - your domain's nameservers need to be configured to be authoritative for your domain - which Google's HonestDNS is not going to claim to be. (Even if you're using GCP.)
- dwild 5y ago
  I think he meant he used the Flush Cache functionality of 8.8.8.8 but emails still failed on Gmail until their cache was invalidated (so Gmail probably is not using 8.8.8.8, or the flush cache doesn't actually works as intended).
  - lathiat 5y ago
    caches are hierachical. Even your local machine most of the time now with recent OS releases will cache records, then your home router or some other DNS server on your network will often cache things before then referring to your ISPs or Googles DNS server. Invalidating the cache at one doesn't invalidate the cache downstream of them if they already looked the record up recently. But it does mean that anyone who hadn't looked up the record will get the correct result straight away.
BenjiWiebe 5y ago
Was it failing at GMail before you flushed at 8.8.8.8? Because then you would have to wait while GMail's own cache expired, assuming they even use the public 8.8.8.8 service.

belter 5y ago

1) What if we purge 8.8.8.8 at 8.8.8.8 ? 2) What if we purge 1.1.1.1 at 1.1.1.1 ? 3) What if we purge both about the other at the same time? 4) What if we purge aaaaaaa! So much time...so many ideas...are they sure they will end up well?

belter 5y ago
I guess the downvotes are about 1 and 2 but ok, I meant dns.google and one.one.one.one
Dylan16807 5y ago
You purge domains, not IPs. And it's not like they need to hold on to any state to work. If you had access you could purge everything and have them start fresh from the root servers, and it would work fine. (As long as the load spike doesn't make it decide to do something dumb, of course.)
kelnos 5y ago
> 1) What if we purge 8.8.8.8 at 8.8.8.8 ? 8.8.8.8 isn't a DNS name, it's an IP address. There's nothing to purge.
- belter 5y ago
  I realize that. Sorry...I meant to say dns.google from dns.google one.one.one.one from one.one.one.one

arantius 5y ago

FYI There's an easier-to-remember URL for Google: https://dns.google/cache https://dns.google/cache The URL above is the documentation of the feature, which happens to also embed it.