501–510 of 519 posts
Earlier quoted context omitted.
I spent some time researching consumer hardware that consistently sacrificed usability for architectural purity. I'll update this reply as soon as I find an example.
I'm trying to figure out how this use of DNS would improve usability for the device owner, and how implementing the DNS client in a standard way could be considered "architectural purity".
Earlier quoted context omitted.
This is extremely annoying. The VPN will switch DNS servers and macOS and Safari work fine, but Chrome will not find internal servers. I assumed it was just a cache, but this makes sense.
I was astonished at how this was handled on the issue tracker. It was closed as "works as designed" even though the design was the problem. https://bugs.chromium.org/p/chromium/issues/detail?id=432236 (I'm obviously a bit biased on the matter because it affected me and cost me a silly amount of time to track down.)
They also claimed Firefox was doing the same thing, which is false and not really sufficient justification for not supporting things that MUST be supported.
[0] https://bugs.chromium.org/p/chromium/issues/detail?id=700354
This should bother people here more than it does. The last thing the Internet needs is even more dependence upon Google. They've made it quite clear through their actions that they're not supporters of a free and open Internet: https://theintercept.com/2018/09/14/google-china-prototype-l... If people don't push back against these kinds of things, Google will continue to abuse their power. There shouldn't be an army o…
I like to use a BSD based router and a PF firewall. My solution:
match in on $i inet proto udp from any to !($i) port {53 123} rdr-to ($i)
The gateway has daemons listening and caching requests for performance. The client has no idea this is happening.
It works great for me.
Earlier quoted context omitted.
We expect that Chromecast connects to Google's servers when you are using Google services. By forcing you to use their DNS service, they can track every non-Google DNS query you make as well, which is all tied to your IP address. It is a form of surveillance of everything that you do on your Chromecast, for which there is no explicit consent. https://security.stackexchange.com/questions/62273/can-dns-s... It is simil…
> By forcing you to use their DNS service, they can track every non-Google DNS query you make as well, which is all tied to your IP address. It's a Chromecast. You literally can't make non-Google queries on it at all in the first place. So what, exactly , is the privacy concern here? What specific flow of events does the Chromecast using 8.8.8.8 impact your privacy?
Earlier quoted context omitted.
We hardcode known good DNS servers in IoT devices that we ship from work because a significant proportion of issues being reported by customers were caused by ISP resolvers doing things they shouldn't - mostly either redirecting all domains to a splash screen telling people about bandwidth quotas/other things, or not respecting the TTL returned by our resolvers, which could cause data to get directed to the wrong pla…
Been there too, sad to say. We haven't gone so far as to hard-code DNS servers yet, but it's shocking how bad some ISPs' DNS support can be. There should be a better way to fight it, but I fear Google may win here because I haven't been able to find anything wrong with the way their servers work. I.e., 8.8.8.8 isn't doing anything evil afaict... Yet.
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…
This isn't a case of an IOT device though. My Chromecast went through massive amount of trouble to use Google's DNS servers, to serve ads behind my pi-hole. It would respect all of my DHCP parameters, but silently ignore DNS settings. It was clearly intentional to serve ads. I had to set up a firewall to force it to use my DNS server. And eventually even that stopped working with an update (which themselves are reall…
here i thought DoH was the panacea, solving all our DNS troubles. but this is one case where DoH doesn't help at all. on the contrary. with DoH we will have no control at all where our apps resolve their DNS requests.
Earlier quoted context omitted.
Yep. In many places in the world, the internet is Facebook/WhatsApp/YouTube and whatever portal each of your apps allows you to peer into.
This is no different than the late 90s, when the Internet was AOL for a huge number of people. In 20 years it'll surely be some other platform, too, as long as the relatively open "Internet" foundation persists.
Smartphone manufacturers can and do have absolute control over the software you run on your device. That was not true in the 90s.