SoylentNews is people
SoylentNews
"Google, this is bogus as hell," Paul Vixie ranted on Internet Engineering Task Force mail list this week. The IETF mail list is where the people who create the internet's technologies converse.
The post was noticed because Paul Vixie is an Internet Hall of Fame engineer known for his pioneering work on the modern Domain Name Service (DNS).
And it is how Google was using DNS in its Chromecast Ultra streaming device that ticked him off.
[...] [Vixie] bought a Google Chromecast. But when he went to set it up, he found it doing something no device in his network is allowed to do: It wouldn't use his own, private DNS server. It would only use Google's public server.
Related: Paul Vixie: New TLDs a Money Grab, and a Mistake
VLC 3.0.0 Released, With Better Hardware Decoding and Support for HDR, 360-Degree Video, Chromecast
Paul Vixie on the Benefits of Running DNS Services Locally
(Score: 2) by Hyperturtle on Monday February 18 2019, @04:20PM
Not much; I was using a nexus 7 tablet that had the celluar option, but I had never bothered to get a SIM chip for it (not even T-Mobile's "free" 200MB per month offer they had for a while).
As a result, it's been WLAN connected only--well, I also have USB wired ethernet connection for it, but that is sort of clunky to connect a tablet like that via a wire. It's what I'd use when scanning wirelessly and transmitting other data over the wire, though, so as to not pollute any wifi traffic or captures of traffic.
But you bring up a good point...for any cellular/LTE device, chances are very good you're not the admin of the device nor able to influence that connection much--unless you use evil hacker tools in violation of various terms of services. You'd need to use a software firewall, or perhaps create a VPN tunnel that has filtering within it to block the google DNS connections. That is assuming the dns lookups go through the tunnel; I couldn't guess if the android OS would try to do an end-run around the VPN or not.
you could try to install iptables or something (or if its already there, modify it) to direct specific IPs through a preferred interface, but I am not sure how it'll behave in the long term. it might give a false sense of security if an update silently reverts the behavior or just defaults it back to how google expects it.