I'm very happy with Pi-Hole. However I'm surprised to have something like 80% or 90% of queries blocked because of one domain, device-metrics-us.amazon.com. It currently has 17,600 hits and the next one on the list is only 172 hits. I have a couple of Echos in my house and an Amazon Fire Tablet. Everything is working fine so I see no need to whitelist the domain. However, given the magnitude of requests, I'd like to ask: do you know what this domain is and why it's requested so much?
Frank, you're lucky it was only 1300 requests in a 24 hour period-- I'm beyond ten times that at nearly 18000! Err, works out to a request every 5 seconds. This thing really wants to 'phone home' pretty badly!
which then led me here. It seems that the Kindle Fire not only needs to phone home often, but starts burning battery if it can't! Really poor design.
I'm just trying to figure out if this was because of a newly-blocked device-metrics-us.amazon.com, or if it was an upgrade to the Fire's OS. I suspect the former.
BTW @showipintbri , the app making the requests (according to the battery monitor I've installed) is Amazon Device Metrics. I would like to try disabling it (I only have one Fire tablet), but it wouldn't surprise me if it breaks things. Somebody want to give it a try??
I can't disable the Amazon Device Metrics app on the Kindle Fire, it just restarts anyway.
So instead I've whitelisted device-metrics-us.amazon.com and then added an /etc/hosts entry for it to point to another machine on my local net that is running an SSL server on port 443. It doesn't seem to be processing any requests (no doubt because it has a bogus certificate), but I'm curious whether this will satisfy my KF enough to make it through the night without a 40% battery level drop. I.e., will the app be satisfied that it is resolving the name, but can't actually connect?
This is really awful behavior of the app anyway -- it means that if your KF is in a marginal or non-existent Wifi zone overnight, its battery will drain quickly, while it's "off", for no apparent reason. Nice design, Amazon!
It's good to see my suggestion started off some research on Kindle Fires and the device-metrics-us.amazon.com domain. I find it irritating that the devices behave in this fashion. However, I can't help but ask, does anyone know why this domain is on the block list? What are the Kindle Fires doing with it? Or, said differently, does the domain really belong on the block lists?
There is no one blocklist - several standard blocklists are installed with pi-hole. They do a good job without problems. But you can add or delete lists as you want or need. It is very easy now to turn on/off installed blacklists or to add new blacklists in the admin menu.
Also you can examine which installed and activated blocklist includes this amazon url...
Frank, yes I understand that there are several standard blocklists. device-metrics-us.amazon.com is found in list.0.raw.githubusercontent.com. However, I ask the same question. Does anyone know why this domain is included? The Kindle Fire tablets hit it like crazy when blocked, and it would be good to know what prompted the domain being on this blocklist in the first place.
More from my testing: Sending requests (via /etc/hosts) to a local server seems to slightly extend battery life -- but it still drops from 100% to 80% in a half-day of being unplugged; far worse than before.
I'm trying the control side of the experiment now, and have whitelisted device-metrics-us.amazon.com completely to ensure that I'm seeing the old battery life.
The terrible thing about this design is that if your kindle lives in a place with poor or no wifi reception, then your battery life is going to suffer as it can't find the device-metrics host. And what, exactly, is it doing contacting this host every 4-5 seconds?
It's been few days since I last responded but I wanted to add: I am seeing the same thing!
My kids (2) have Kindle Fire Tablets. I'm seeing both collectively hitting over 50,000 DNS requests per day.
I too noticed my kids tablets battery life draining completely in a day, even when sitting idle and not being used.
What I tried was turning off wifi on the kids tablets. This seems to extend the battery life (like it originally was), not because it's not using wifi but because its not generating over 25,000 DNS requests and web-requests.
Another thing I found was dis-associating from the wifi also extends the battery life, again, this is because it has no way to make the DNS requests. But when wifi is on and you are connected to a network, it will constantly try to connect draining battery.
The next experiment is white-listing the domain and seeing my device battery metrics after.