[ NNSquad ] Re: Comcast files "recommended practices" draft RFC with IETF for DNS Redirection

["David P. Reed" <dpreed@reed.com>]

I have to say this has been a very helpful (to me at least) and 
generally constructive discussion of OpenDNS's technology and business 
model.

While it does not directly bear on ISP provision of non-standard DNS 
services as in the recommended practices RFC, I think the discussion has 
illuminated both concerns and some of the less clear aspects of 
OpenDNS's technology and business practices.

I've made my concerns pretty clear on both the ISP offerings (which 
differ because they are "forced" by default on their entire customer 
base via DHCP or in the case of some hotel operators, forced by 
intercepting all UDP packets targeted at *any* host with the DNS service 
port number and forging responses), and on OpenDNS.

In fairness, I haven't mentioned on the open list that there are "pure" 
(standards based) recursive DNS offerings that anyone can try to adopt 
(except in the "interception" case, which the RFC does not mention).  
One such that I have used is provided by DynDNS.com, but it costs about 
$2.33/monthfor one client.  DynDNS.com claims that they do not share 
data with *anyone*, nor do they use the data for any purpose.  AFAIK, 
they are extraordinarily reputable and careful.

But I'll consider the discussion done for now.

    [ As do I.  Thread closed.

         -- Lauren Weinstein
            NNSquad Moderator ]