4 ms·
I love Chromecasts and brining Google Cast into Chrome made me quite happy since the integration with Hangouts (you can cast a tab into a hangout if the meeting
by realityking 10y ago
I love Chromecasts and brining Google Cast into Chrome made me quite happy since the integration with Hangouts (you can cast a tab into a hangout if the meeting is part of your Google Calendar) is terrific.
However as someone who helps out with the company's network, they are infuriating:
- They ignore the DHCP given DNS Servers instead using Google's. I'm sure the same is true for NTP though I haven't bothered testing that.
- They use mDNS and DNS-SD but not DNS-SD Wide Area Discovery. This makes subnetting more difficult and increases broadcast traffic quite a bit.
- Not a complaint, more a wish, but a PoE version of the Ethernet adapter would be immensely helpful.
- hackuser 10y agoOT: If someone wanted to block connections to Google's DNS servers, can it be done reliably? Is there a known, static range? AFAIK Android also uses Google's DNS servers, and it's hard coded into the OS, and the client pings the server before any software firewall can load at boot. (Allow me to reemphasize: AFAIK; if someone knows more I'd appreciate it.)
- viraptor 10y agoI don't know how the mobile networks configure the dns, but on WiFi android uses whatever dns server is advertised via dhcp.
- izacus 10y agoAndroid yes, Chromecast no. It's hardcoded to defeat DNS-level location spoofing for Netflix and similar services.
- tracker1 10y agoYou can capture all DNS outbound (port 53) traffic not to/from your local DNS server and redirect it to your local/internal DNS server if you really wanted to. This is often done in order to jail/freeze all traffic until authenticated as well as whitelist certain traffic for the purpose of authentication.