My Chromecast Ultra would not start until I began answering 8.8.8.8

Re:My Chromecast Ultra would not start until I began answeri... by AnIdiotOnTheNet on Friday February 15, 2019 @12:54PM (#19173038)

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.

[ Parent | on HN ]

Re:My Chromecast Ultra would not start until I began answeri... by Arnt on Friday February 15, 2019 @01:43PM (#19173517)

Do you happen to be the admin at the meeting venue that discarded my SRV and DNSSEC lookups? What were the reasons you did this, if so?

[ Parent | on HN ]

Re:My Chromecast Ultra would not start until I began answeri... by AnIdiotOnTheNet on Friday February 15, 2019 @03:13PM (#19174286)

Use the guest WiFi, that's what it's there for.

[ Parent | on HN ]

Re:My Chromecast Ultra would not start until I began answeri... by Arnt on Saturday February 16, 2019 @02:39PM (#19180519)

Does that have a sensibly working resolver?

In my haphazard experience, the networks that block access to UDP port 53 are more than likely to have gelded broken name servers that e.g. serve empty NXERROR results for anything but A/TXT, and receptionists that say, "uh, let me check" and then check that their browser can open the google home page. (Insert invectives here.)

I've seen be fixed. Once. One meeting I attended started with a quite broken network, but it was an IETF meeting, and the IETF tools team reconfigured the AP channel layout, the DHCP server and the caching name server at that hotel and after that it was fine.

[ Parent | on HN ]