# Tado insane DNS lookups **URL:** \ **Category:** Apps\ **Created:** [February 27, 2019, 1:36am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782 "2019-02-27T01:36:57Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Peter\_Thornton](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_thornton/32/5109_2.png) [@Peter\_Thornton](https://community.homey.app/u/Peter_Thornton)\ **Post date:** [February 27, 2019, 1:36am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/1 "2019-02-27T01:36:57Z")
Unless my Pi-hole DNS server is wrong, the Tado App on my Homey makes 200.000 DNS requests per 24 hours. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/5/5f2dd4e121419262bef02e716f87ff6e4825708e.png) Anyone else noticed this? ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [February 27, 2019, 9:01am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/2 "2019-02-27T09:01:21Z")
Not myself but I’ve seen reports in the past where numerous requests for a Philips Hue were done ([meethue.com](http://meethue.com) if I remember correctly) You would expect some dns caching, the ttl on the [my.tado.com](http://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. ---
**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\ **Post date:** [February 28, 2019, 11:11am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/3 "2019-02-28T11:11:51Z")
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](http://api.ring.com)… so maybe its normal behavior? ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [February 28, 2019, 11:20am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/4 "2019-02-28T11:20:25Z")
Do you have numbers? How many requests are we talking about? [api.ring.com](http://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. ---
**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\ **Post date:** [February 28, 2019, 11:23am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/5 "2019-02-28T11:23:33Z")
there you go ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/2X/3/3e389a6b261e36eee739d9c00dd7e62fc9adadc1.png) ---
**Author:** ![Mark\_Homey](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mark_homey/32/9202_2.png) [@Mark\_Homey](https://community.homey.app/u/Mark_Homey)\ **Post date:** [February 28, 2019, 11:33am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/6 "2019-02-28T11:33:25Z")
My Homey does also 2 DNS requests each 5 seconds to [api.ring.com](http://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. ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [February 28, 2019, 2:47pm UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/7 "2019-02-28T14:47:21Z")
Well yeah, trying to connect to [api.ring.com](http://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. ---
**Author:** ![Peter\_Thornton](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_thornton/32/5109_2.png) [@Peter\_Thornton](https://community.homey.app/u/Peter_Thornton)\ **Post date:** [February 28, 2019, 8:23pm UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/8 "2019-02-28T20:23:01Z")
TTL of 60 seconds… But why? ---
**Author:** ![Jamie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jamie/32/5274_2.png) [@Jamie](https://community.homey.app/u/Jamie)\ **Post date:** [March 1, 2019, 12:01am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/9 "2019-03-01T00:01:23Z")
load balancer? ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [March 1, 2019, 7:18am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/10 "2019-03-01T07:18:14Z")
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. ---
**Author:** ![bvdbos](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bvdbos/32/2352_2.png) [@bvdbos](https://community.homey.app/u/bvdbos)\ **Post date:** [March 1, 2019, 8:00am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/11 "2019-03-01T08:00:31Z")
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… ---
**Author:** ![ralfvd](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ralfvd/32/16441_2.png) [@ralfvd](https://community.homey.app/u/ralfvd)\ **Post date:** [March 1, 2019, 8:32am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/12 "2019-03-01T08:32:32Z")
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](https://www.ctrl.blog/entry/dns-client-ttl) ---
**Author:** ![Ruud\_Verrijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruud_verrijk/32/903_2.png) [@Ruud\_Verrijk](https://community.homey.app/u/Ruud_Verrijk)\ **Post date:** [April 14, 2019, 8:46am UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/13 "2019-04-14T08:46:04Z")
Yes, here as well. Pi-hole logs an incredible number of DNS requests to tado home base. ---
**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\ **Post date:** [April 24, 2019, 6:14pm UTC](https://community.homey.app/t/tado-insane-dns-lookups/9782/14 "2019-04-24T18:14:03Z")
In the [Release Notes for Homey v2.1.2-rc.3](https://firmware.athom.com/) - [Core] DNS TTLs are now respected and cached