Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 11 submissions in the queue.

Paul Vixie Complains about Chromecast's Use of Google DNS

posted by martyb on Sunday February 17 2019, @09:12AM   Printer-friendly
from the pegging-the-bogosity-meter dept.

takyon writes:

'Google, this is bogus as hell' — one of the fathers of the internet blasts Google for how Chromecast behaves on his home network

"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

Original Submission

 
This discussion has been archived. No new comments can be posted.
Paul Vixie Complains about Chromecast's Use of Google DNS | Log In/Create an Account | Top | 50 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2, Disagree) by exaeta on Sunday February 17 2019, @06:20PM (4 children)

    by exaeta (6957) on Sunday February 17 2019, @06:20PM (#802572) Homepage Journal
    I don't see any obligation on part of pcrogrammers to use a local dns resolver. It's kind of a bad design, tbh. I don't blame google for wanting to avoid T-Mobile, AT&T et al. intercepting dns requests and returning bogus crap.
    --
    The Government is a Bird
    Starting Score:    1  point
    Moderation   0  
       Disagree=1, Total=1
    Extra 'Disagree' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 1, Insightful) by Anonymous Coward on Sunday February 17 2019, @06:42PM

    by Anonymous Coward on Sunday February 17 2019, @06:42PM (#802582)

    ... I don't blame google for wanting to avoid T-Mobile, AT&T et al. intercepting dns requests and returning bogus crap.

    Err, they still can...the phone companies can still play silly fsckers with the traffic on their networks bound to the google servers, though I think most of them, by now, probably have agreements in place not to do such kind of things with google traffic.

  • (Score: 2) by exaeta on Sunday February 17 2019, @06:58PM

    by exaeta (6957) on Sunday February 17 2019, @06:58PM (#802586) Homepage Journal
    *programmers. I wish we could edit comments. :(
    --
    The Government is a Bird

  • (Score: 2) by zocalo on Sunday February 17 2019, @11:10PM (1 child)

    by zocalo (302) on Sunday February 17 2019, @11:10PM (#802648)
    How about if you ignore what you are told via DHCP your device might not work? Vixie seems to be only allowing outgoing DNS unless originated by his own resolver and is presumably dropping the rest on the floor via firewall egress filtering. By assuming that DNS requests to 8.8.4.4 and 8.8.8.8 would be allowed to freely traverse the firewall, regardless of what they were told by DHCP and in contravention of BCPs regarding egress filtering, it's hardly surprising that the Chromecast did not work.

    A Chromecast allowing a user to choose between his own DNS (regardless of how that is configured on the device) or letting the Chromecast use a preconfigured default of Google's DNS is one thing. Ignoring a user's request to do one thing using your own choices anyway is something else, and that is broken by design.
    --
    UNIX? They're not even circumcised! Savages!

    • (Score: 2) by exaeta on Monday February 18 2019, @01:07AM

      by exaeta (6957) on Monday February 18 2019, @01:07AM (#802704) Homepage Journal
      Network firewalls and blocking ports are bad practice. They shouldn't be utilized, and it's your fault if you break a device by blocking traffic.
      --
      The Government is a Bird