Re:My Chromecast Ultra would not start until I began answeri...
by vbezhenar on Friday February 15, 2019 @09:34AM
(#19171184)
"Broken" ISP are likely to intercept DNS requests, so really the only option against them is something like DNS over HTTPS.
[ Parent
| on HN ]
Re:My Chromecast Ultra would not start until I began answeri...
by scrollaway on Friday February 15, 2019 @09:40AM
(#19171231)
[citation needed] on that "likely" word. I've seen instances of that, but they're extremely rare because intercepting DNS altogether is a fucked up thing to do for an ISP.
Seen far, far more instances of:
- ISPs shipping shitty network devices / awful factory settings
- ISP's own DNS servers being terrible in various ways
- Uncle Steve "the IT guy of the family" having messed with the network settings and nobody knows why 1 youtube video in 20 doesn't load but we just ignore it.
Re:My Chromecast Ultra would not start until I began answeri...
by loeg on Friday February 15, 2019 @12:32PM
(#19172830)
Centurylink hijacks 100% of real NXDOMAINs to their DNS servers and replaces them with a redirect to their internal portal. They "have" a configuration knob to disable the behavior, but it doesn't work or isn't reliably persisted; it never sticks. Big residential ISP.
Re:My Chromecast Ultra would not start until I began answeri...
by igetspam on Friday February 15, 2019 @10:05AM
(#19171430)
TimeWarner and Comcast have both done it toe. TWC did of to let me know of a TOS violation and Comcast uses it as part of their setup. If you don't allow them to hijack DNS and show you things that you have to click through, you may find yourself unable to route traffic at all until you call them. I've dealt with this with every move in CA (about a half dozen times) and my move to TX. Seems pretty likely to me.