Whenever a device needs to connect to a web domain, the first thing it has to do is retrieve that domains IP address. Thats a DNS request.
While I don’t remember which domains exactly (this was 5+ years ago when I last checked); just the fact that it’s reaching out to external connections 20k+ times a day is concerning.
For context; my entire network has made 28k dns requests in the last 24hrs. Thats 3 mobile phones that are in use constantly, three PCs, and a handful of IOT devices like smart bulbs/switches.
20k from one device is A LOT.
It’s primarily an idle device that’s awaiting a voice command. Supposedly it’s processing audio locally to find the wake word ‘ok google’ and only then uploading the audio to be processed as a voice command on googles servers. So what’s it uploading/connecting to 20k times a day while it’s suposed to be idle…?
Because its recording every single word you say waiting for the trigger word to send the black van to your house (the trigger word is opposite of “lick dear leaders boots”).
Same experience here. DNS server was omething like goooooooogle.com for me.
Blocking them made the devices malfunction, I believe the speakers werent fully aware of each other anymore, so speaker groups got messed up in all sorts of ways.
What does that mean exactly? Like it’s trying to connect to where? Why?
Whenever a device needs to connect to a web domain, the first thing it has to do is retrieve that domains IP address. Thats a DNS request.
While I don’t remember which domains exactly (this was 5+ years ago when I last checked); just the fact that it’s reaching out to external connections 20k+ times a day is concerning.
For context; my entire network has made 28k dns requests in the last 24hrs. Thats 3 mobile phones that are in use constantly, three PCs, and a handful of IOT devices like smart bulbs/switches.
20k from one device is A LOT.
It’s primarily an idle device that’s awaiting a voice command. Supposedly it’s processing audio locally to find the wake word ‘ok google’ and only then uploading the audio to be processed as a voice command on googles servers. So what’s it uploading/connecting to 20k times a day while it’s suposed to be idle…?
I don’t know exactly. That’s the problem.
Because its recording every single word you say waiting for the trigger word to send the black van to your house (the trigger word is opposite of “lick dear leaders boots”).
All of these devices are spyware.
Same experience here. DNS server was omething like goooooooogle.com for me.
Blocking them made the devices malfunction, I believe the speakers werent fully aware of each other anymore, so speaker groups got messed up in all sorts of ways.
I use Bluesound speakers and modules now.
To be fair, IoT devices should be making exactly zero DNS requests, unless maybe you set up a proper domain name for your Home Assistant server.