(Google - of course - does the technically correct thing)
That being said, I can still get behind at least choosing to let someone hijack those pages, rather than sticking with a company that does it automatically.
At some point in time I'd have said this would increase your DNS latency, but given the poor level of service that many ISP servers provide, I don't think that's true anymore. Though I have no data to back this up, I suspect many home users visit a fairly small set of websites and so DNS caching would work very well.
I have never seen an Israeli ISP do that. (Although, there were reports a few years ago that Bezeq intercepted .torrent files to add their own trackers to the file.)
Also because Comcast DNS sucks horribly and times out with upsetting regularity.
There is, as far as I know, no switch to make their DNS more reliable, though.
I take it you've logged into your comcast.net account and the box to disable it isn't there for you?
A lot of them already hijack port 80 and inject random junk in there which is why HTTPs is the way forward.
That's a pretty bold claim. Other than free wifi at hotels, I've never seen an ISP use transparent proxying to intercept pages and serve ads.
Do you have any examples?
Basically they mangle the HTML and slap in their own banner which means they must be doing some kind of stream inspection and processing to manage this. I do not have a proxy configured, and requests don't indicate that this is being done.
I personally use it because I am extremely uncomfortable with my ISP catching mistyped URLs and redirecting me to a page filled with ads, searches, and other bogus things.