DNS: Optimise switch time
I have a question regarding DNS. We are going to switch a DNS from one source to another (meaning the content of DNS record). And this switch is extremely important for us. So, the question is do we just change a DNS record or maybe, there is something that we can do to help it propagate faster, improve the process so to say?
8 Replies
Is the DNS record Proxied(Orange-Clouded)?
@Hard@Work yes, it is
Then it should happen within a few seconds globally. Proxied Record changes happen really fast
Assuming you are changing Proxied-to-Proxied
@Hard@Work Not sure, but I believe it will be proxied as well.
Thanks for quick reply, appreciate it!
Just wondering for myself, if not proxied, are there any workarounds to make it faster? Maybe you can point me to some articles or something like that?
And one more question, if we change the record type? A -> CNAME, does that matter? (still being proxied)
It shouldn't, afaik? Externally, it should reuse the same record
Not really a way to speed it up. You are kind of at the mercy of the DNS resolvers your customers are using
Keeping your TTLs low can help, but a lot of resolvers cache for a long time anyway
yeah, also was wondering about TTL.
Okay, I got your point. Thank you!
are there any workarounds to make it faster?Cloudflare's public dns 1.1.1.1, and Google's 8.8.8.8 have public clear cache pages, https://developers.google.com/speed/public-dns/cache, which can help, but those aren't going to be the issue most of the time, if your audience is humans they're going to be using their ISP provided DNS which some ignore TTLs to begin with, and don't have public purge pages
@Chaika okay, thank you!