Scott, If you're going to blatantly copy what others have written on another mailing list, please at least have the common decency to attribute it to the original author, and/or get the original authors permission first.
Scott. On Thu, Nov 19, 2009 at 5:31 PM, Scott Weeks <[email protected]> wrote: > > > >From AUSNOG: > > > On Thu, Nov 19, 2009 at 2:08 PM, Paul Foote <[email protected]> wrote: > > All that's left for them to complete the "404" strategy is to put > transparent proxies in place that redirect on real 404's :P > > Did nobody learn the lessons from when Verisign did this with .com ? > baah. > > > In fairness (and I use that term loosly) to BigPond, this is probably a > little different to what Verisign did. > > I haven't seen the BigPond details, but I have seen what Comcast are doing > on my US cable connection, and I presume BigPond is doing something similar. > > The major differences between the two are : > * Only responds for "www" addresses. a lookup for "non-existantdomain.com" > will still return an NXDOMAIN, but "www.non-existantdomain.com" returns > their search page. This means that (the majority of) things like > RBL/anti-spam/etc things which broke under Verisign's redirection no longer > break. > * It's only home users. Business plans/etc are not redirected. Obviously > this is different to Verisign where everyone was hit. > * You can turn it off, and the page you end up on even gives you the > details on how to turn it off. > > Also despite claims to the contrary, Comcast are not actually > "intercepting" DNS traffic - or at least they aren't for me. They are only > doing this for traffic sent directly to their DNS servers, and pointing to > another DNS server works as expected, as does running your own resolver. > > > I'm still not saying that it's a good thing for them to be doing, but it's > not quite as bad or destructive as Verisign's move was... > > > > > >
