Mike Hearn [ARCHIVE] on Nostr: 📅 Original date posted:2011-08-03 🗒️ Summary of this message: Some ISPs may ...
📅 Original date posted:2011-08-03
🗒️ Summary of this message: Some ISPs may cache DNS for up to a week, ignoring TTL, but it's unlikely for professional ISPs as it causes issues with popular sites. Randomizing DNS requests is a good idea.
📝 Original message:>
> Someone I know who runs a moderately large website told me that some ISPs
> cache DNS for as long as a week without regard to TTL.
>
We track DNS disobeyers at Google, as we use it for load balancing (along
with many other large sites).
I'd be kind of surprised if any large/professional ISP disobeyed the TTL
that badly, because it would cause frequent problems reaching popular sites
like anything hosted on Google or Akamai. But randomizing the DNS request
isn't a bad idea.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110803/bf787659/attachment.html>;
🗒️ Summary of this message: Some ISPs may cache DNS for up to a week, ignoring TTL, but it's unlikely for professional ISPs as it causes issues with popular sites. Randomizing DNS requests is a good idea.
📝 Original message:>
> Someone I know who runs a moderately large website told me that some ISPs
> cache DNS for as long as a week without regard to TTL.
>
We track DNS disobeyers at Google, as we use it for load balancing (along
with many other large sites).
I'd be kind of surprised if any large/professional ISP disobeyed the TTL
that badly, because it would cause frequent problems reaching popular sites
like anything hosted on Google or Akamai. But randomizing the DNS request
isn't a bad idea.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110803/bf787659/attachment.html>;