3 ms·
It's also partly because so many isps got tired of their caches being basically useless because of so many people setting obscenely low ttls too. There's no wi
by simcop2387 5y ago
It's also partly because so many isps got tired of their caches being basically useless because of so many people setting obscenely low ttls too. There's no winning answer.
- yjftsjthsd-h 5y agoIs DNS truly so high load that they need substantial caching? I mean, DNS responses should be kilobytes on the high end; it seems like they should barely register on overall traffic.
- CaliforniaKarl 5y agoImagine a home with some IoT devices: A smart thermostat, a smart TV, a smart doorbell, and three cameras. The thermostat connects out every 30 seconds to send a temperature report, and to check for settings changes. The smart TV, every 30 seconds, sends a compressed snapshot of the image currently being displayed, for ad generation. The doorbell starts a new connection to stream video whenever movement is detected. The cameras do the same. Each device was built without any thought to DNS caching. As such, every new connection is going to trigger a new DNS lookup. Multiply that by however many homes are in the area, and the load really starts going up. Especially because each lookup from the device causes a series of lookups to happen on the recursive DNS server.