3 ms·
Absolutely. My friend worked for an ISP in Alaska. They set their TTL to 48 hours for all records regardless of what the DNS said, because they didn't have th
by jedberg 5y ago
Absolutely. My friend worked for an ISP in Alaska. They set their TTL to 48 hours for all records regardless of what the DNS said, because they didn't have the bandwidth to pull updates more often than that.
Also, when I worked at reddit I had to change the IP for reddit.com in 2007. I set up a cache on the old IP to redirect any old traffic. Also, a week before the switch I had pulled the TTL down to 5 seconds.
After I made the change, only 40% of the traffic shifted after a minute. That means at least 60% of the people on the internet were ignoring my 5 second TTL if not more.
After a day 10% of the traffic was still going to the old IP. It took more than 48 hours for 99% of the traffic to switch. And after a month I still had about 20 hosts hitting the old IP (probably scripts that were hard coded with the old IP).
At Netflix we had similar issues with lots of stragglers when we changed IPs.
So yeah, a lot of resolvers ignore TTL.
- micw 5y agoI wonder what kind of ISP it was with to few bandwidth for proper DNS ^^ And I'm really curious which other ISPs are running such setups that you had to deal with and for what reason they do so.
- jedberg 5y agoA small ISP in the early 2000's. :) I don't really know the cause of the other problems, but I'm guessing it was mostly browser and OS caching and not ISP caching.
- watermelon0 5y agoDon't really know how accurate this is, but I remember reading about some resolvers ignoring too low TTLs.
- jedberg 5y agoIt's quite possible that the 5 second TTL was a foot-gun. It was best practice at the time but not necessarily the right thing to do!