Unless my Pi-hole DNS server is wrong, the Tado App on my Homey makes 200.000 DNS requests per 24 hours.
Anyone else noticed this?
Not myself but I’ve seen reports in the past where numerous requests for a Philips Hue were done (meethue.com if I remember correctly)
You would expect some dns caching, the ttl on the my.tado.com record is 60 seconds but if your numbers are correct there are (averaged) over 2,3 requests per second and not the 1 per 1440 seconds if the ttl was honored.
I don’t have a tado, but my homey is doing most DNS requests in my environment. I’m working from home and am constantly online, but still the homey does a lot more requests (I now realize it could have something to do why my working pace…).
Most requests within my env go to api.ring.com… so maybe its normal behavior?
Do you have numbers? How many requests are we talking about? api.ring.com has a 5 minute ttl so anything above 288 requests in 24 hours does indicate something fishy is going on with caching of dns information.
My Homey does also 2 DNS requests each 5 seconds to api.ring.com, 1440 requests each hour. In my opinion there is no way to change this because this is programmed behaviour in the Ring app.
Well yeah, trying to connect to api.ring.com may be programmed to happen 2 times in 5 seconds, but when a request is made and the dns info is retrieved I would not expect another dns request until the ttl on the record expires, I would expect the info to be cached so no new dns query is required.
TTL of 60 seconds… But why?
load balancer?
But thats on the server side, doesn’t have anything to do with a client not doing any caching.
Maybe it’s because apps are sandboxed and there’s no method for caching implemented.
Should be done on OS-level. But the DNS-lookups aren’t an issue in itself, calling the API (using the DNS-lookup) that much is the real issue I think. I did see an app with DNS-caching iirc, I’ll look it up tonight…
2 Likes
Many clients don’t do DNS caching, they just continue querying the DNS server. The DNS server will probably honor the caching ( so the pi-hole will not forward the DNS query to an outside resolver) .
This is a nice overview of honoring TTL caching: https://www.ctrl.blog/entry/dns-client-ttl
1 Like
Yes, here as well. Pi-hole logs an incredible number of DNS requests to tado home base.
