3 ms·
You seem to be taking offense to something that wasn't said. The term "hijacking" is used here in much the same sense as "signal hijacking" or the program Audio
by chc 15y ago
You seem to be taking offense to something that wasn't said. The term "hijacking" is used here in much the same sense as "signal hijacking" or the program Audio Hijack. The relevant part of the "hijack" imagery is forcibly taking over the way a transport. It essentially means they are causing DNS requests to return against-spec responses.
- pbhjpbhj 15y agoHyperbole blah-blah-blah. >they are causing DNS requests to return against-spec responses // That's part of their service. If there was no way to switch it off then I can understand being annoyed but you can just choose to use your ISP's DNS. It just appeared to me that both comments concerning this were of the form "ZOMG they has borken my internetz"; could be I read the tone wrong. So anyway, for the service that OpenDNS are offering is it wrong of them to simplify the situation for users making mistakes entering domain names in their browser?
- chc 15y agoI think "wrong" is a good word for it. Users typing things into an address field in a Web browser is not the only use case for DNS, but this breaks DNS for the whole system, which is the wrong solution. Correcting mistakes in the address field is something browsers should take care of. Firefox and Chrome both do — I know Safari doesn't, and I can't remember what IE does. In fact, Chrome has to employ a rather ugly hack to work around this behavior from noncompliant DNS servers.
- pbhjpbhj 15y ago>not the only use case for DNS // Of course. But I think that's exclusively the use case that OpenDNS target in their consideration of non-resolving domains.