my family is moving into a much bigger house than we used to have. we use amazon echos as an intercom system through the announcement feature. because our house is bigger, i’m being forced to get one myself for my room. i haven’t needed one for years because i use their app on my phone and i can see their announcements as a notification and i can also kill off most of its tracking by DNS. unfortunately my parents don’t understand this and are forcing me to get one. what can i do to limit its tracking?
thanks for the suggestion! as for nextDNS, i was already thinking of using this however you cannot change the DNS servers used on alexa devices. i was thinking of setting up openWRT on a pi and using that as a router specifically for our alexa devices with a nextDNS profile installed, but im not sure if alexa’s default to the router’s DNS or amazon’s. even if it does use the router’s DNS, does it backup to Google’s DNS (8.8.8.8) like Roku does?
With opnwrt you can do DNS hijacking, where you force redirect DNS requests for other servers to your own DNS server. This works as long as they aren’t encrypted (DNS over HTTPS or TLS), which most devices don’t use.
I specify my LAN DNS servers (2 pihole instances, main + a backup for redundancy) in my routers DHCP settings, so they are the DNS servers handed out to all LAN clients; then I have an iptables rule on the router blocking all port 53 traffic from leaving the network unless it came from those LAN DNS servers. This means only the piholes can reach external dns; everything else is required to use the LAN DNS servers or receive no response. Then the piholes have full control over what can and cannot resolve to an IP.
I haven’t found a device that doesn’t work with this setup. I used to have a couple google homes before I wised up, they worked fine behind this setup.
https://youtu.be/EdzDCkFaskc?si=F8FB0Xn28YeZ9N90
I’m doing this and it works great.
When my server turns off everything stops working which is interesting.
