How to Fix DNS TTL Issues

The client has cached the knowledge that this domain supports quick and HTTP three, but then it pointed to a different IP that doesn't. And all of a sudden things break. So what happened if you now turn around and do another DNS, right? You're pointing to another CDN that happened to not support quick. But guess what? You're still using the same domain. They solve this by making the DNS TTL very close to the alt serviceTLT. That's basically the most interesting thing here. I never thought about this before. Apparently there is a discussion going on with this.

Transcript

Play full episode

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.