251–260 of 519 posts
Earlier quoted context omitted.
First they came for the appliances I don't want or need, because I don't use appliances I don't want or need. This has been discussed to death. Slippery slope, etc., etc.
I disagree. People who care about not hitting 8.8.8.8 simply do not own a Chromecast.
I'm always shocked at how easy it is for people to fall into the "Google is evil!!1" trap on such trivial stuff (and funnily enough, much more serious privacy issues related to Google are ignored/downvoted). Hardcoded DNS servers are common. Extremely common in a bunch of IOT devices, given how broken some ISPs are. This is a non-story and the only reason it's being upvoted is because Google is doing it, and they als…
I can totally see how they and other IoT vendors would want to do that. What boggles my mind is that so many people believe the feature implemented was "Use 8.8.8.8 and break otherwise so we can trojan our DNS into places" instead of "Hardcode 8.8.8.8 so it works in most cases".
Yeah. I know we'd all want to believe that the response and reaction here would be the same if it was pointed to 1.1.1.1, but... yeah, we know better. Everyone would point out that consumer ISPs server polluted data and that Cloudflare clearly provides better service, and relying on that instead of the local garbage is quite obviously a benefit to the device user. But this is Google, and people here have iPhones, so…
It's not unreasonable to attempt to use DHCP provided DNS servers. It's not unreasonable to use fallback DNS servers when the DHCP provided servers don't work. It would be a bit strange, but maybe not altogether unreasonable to run a fully recursive DNS client with root.hints and what not. I guess you could argue over reasonableness of favoring the fallback DNS over DHCP. It's not reasonable to ignore DHCP when the f…
Earlier quoted context omitted.
> Or is there a legitimate usecase for such behaviour? Yes, to track you better.
Or to speed up the Internet experience. https://googleblog.blogspot.com/2009/12/introducing-google-p...
Kind of like they started Knol to compete directly with Wikipedia.
Earlier quoted context omitted.
This is an incredibly generous reading of the situation that, as far as I can tell, has no basis in reality. Google is circumventing how the internet works at pretty basic level by not respecting users' DNS preferences in favor of their own.
The consumer of the DNS is the Chromecast. Its preference is 8.8.8.8 .
Knowing who he is, my takeaway should be, "Wow! An Internet Hall of Famer weighing in against a Google product!" But my actual takeaway is, "Legends of the CS world write informal, pithy rants to Google just like the rest of us mortals."
Earlier quoted context omitted.
I too have written code that asks 8.8.8.8 and 8.8.4.4, because the DNS server I get from DHCP frequently is so brain-damaged. (SRV records, what's that?) I asked both in parallel. On one hand it feels wrong to not ask in parallel. On the other, $%#@%#$%!$@# the %$#%#$%^$#@%#$! packet filters that block DNS packets to everyone except the local brain-damaged resolver. Or even redirect. If Google will fight that fight I…
As someone who has had to block and redirect DNS traffic, there are reasons we do this and if you have a problem with it then you should contact the admins about it. If you're unwilling to do that, maybe you shouldn't be doing what you're trying to do at work.
Earlier quoted context omitted.
Came here to say exactly this. Why even make a fuss about it? Bro, do you even NAT? The argument is Google can record what you're sending your Chromecast. Well, (sorry for the crudeness) no shit... You're using Google hardware. If you're going to act like the DoD and not use Huawei switches, then don't use Huawei switches. If you so choose, you must look at Google as malevolent as the US DoD would see an attacking na…
Cool, I'll be sure to tell my mother-in-law that if she's concerned about her privacy, she just needs to use NAT "bro".
Earlier quoted context omitted.
OK but if that "known good" DNS server goes down or isn't available, you still have others you can fall back to. The device shouldn't just become completely useless. But that's what Google is doing here. It's their DNS servers or none, it seems.
I too have written code that asks 8.8.8.8 and 8.8.4.4, because the DNS server I get from DHCP frequently is so brain-damaged. (SRV records, what's that?) I asked both in parallel. On one hand it feels wrong to not ask in parallel. On the other, $%#@%#$%!$@# the %$#%#$%^$#@%#$! packet filters that block DNS packets to everyone except the local brain-damaged resolver. Or even redirect. If Google will fight that fight I…
Evidently, they are:
https://en.wikipedia.org/wiki/DNS_over_HTTPS
https://developers.google.com/speed/public-dns/docs/dns-over...