[103393] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: NXDOMAIN data needed for survey

daemon@ATHENA.MIT.EDU (Ray Demain)
Fri Mar 28 12:13:51 2008

Date: Fri, 28 Mar 2008 11:12:49 -0500
From: "Ray Demain" <raydemain@gmail.com>
To: nanog@merit.edu
In-Reply-To: <20080328020944.GC52132@elvis.mu.org>
Errors-To: owner-nanog@merit.edu


------=_Part_23713_20087574.1206720769588
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Bill,

Isn't it funny though that OpenDNS is funded by the same group who funded
Paxfire?

www.minorventures.com

OpenDNS can be an angel on one shoulder while Paxfire is on the other,
right?

Ray



On Thu, Mar 27, 2008 at 9:09 PM, bill fumerola <billf@mu.org> wrote:

>
> [ disclaimer: i work for opendns. ]
>
> On Fri, Mar 21, 2008 at 05:53:15PM -0400, Martin Hannigan wrote:
> > >  I think it's best that we let David Ulevitch and the crew @ OpenDNS
> make
> > >  the money that is to be made off this. He's doing good while doing
> well.
> >
> > Why shouldn't anyone be able to "make the money"? The problem with
> > that post wasn't that he was advocating law breaking, it was that it's
> > a marketing missive and inconsistent with community norms, IMHO. That
> > doesn't mean that it's illegal, and it certainly doesn't mean it's ok
> > for one "good guy" to be allowed to profit and one unknown not to.
> > Setting classes of who can profit from NXDOMAIN data creates
> > unfairness in the system and it should be all or none.
>
> now that our name has been brought into this, i think it's only fair to
> say: the NXDOMAIN data we know about is when a user's resolver asks our
> recursive servers for a record and NXDOMAIN is the end result of what
> our resolvers discover.
>
> at that point, we optionally point you at a lander page w/ search results
> and ads and all that jazz based on the words in the record you
> [mis-]typed.
> note the optionally. if you want, we'll just return NXDOMAIN. you can
> configure this. you can configure it per-ip, per-prefix, etc.
>
> now, on to what we do or could do with that data:
>
> we do not sell and have never sold NXDOMAIN data. nor do we register
> domains based on NXDOMAIN information. the non-OpenDNS company who sees
> the original request that produced the NXDOMAIN that failed (which may
> or may not even be a valid hostname) is our advertising partner.
>
> they get that data after we've transformed the original request into
> their API to send to them as keywords so they may return appropriate and
> relevant ads.
>
> so, to recap:
> nope, we don't sell NXDOMAIN data. we don't sell any other data either.
> yes, some revenue comes from typos/mistakes. you knew that already.
> yes, you can even change that behavior and just get NXDOMAIN.
>  that means your typos gain us nothing. you get our service for free.
> yes, you opt-in to our service in the first place.
> yes, we have a privacy policy that says this better than i can.
>
> > What you really want to look at is privacy policy. Not all of the good
> > guys are actually good guys in that respect.
>
> http://www.opendns.com/privacy/
>
> it looks pretty good to me. i read it before i agreed to employment.
>
> -- billf >at< opendns.com // opendns network engineering
>
> p.s. since i rarely if ever post, i have to make the shameless, shameless
>     plug: <peering@opendns.com>. we're in peeringdb too.
>
>
>
>

------=_Part_23713_20087574.1206720769588
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Bill,<br><br>Isn&#39;t it funny though that OpenDNS is funded by the same group who funded Paxfire?<br><br><a href="http://www.minorventures.com">www.minorventures.com</a><br><br>OpenDNS can be an angel on one shoulder while Paxfire is on the other, right?<br>
<br>Ray<br><br><br><br><div class="gmail_quote">On Thu, Mar 27, 2008 at 9:09 PM, bill fumerola &lt;<a href="mailto:billf@mu.org">billf@mu.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
[ disclaimer: i work for opendns. ]<br>
<div class="Ih2E3d"><br>
On Fri, Mar 21, 2008 at 05:53:15PM -0400, Martin Hannigan wrote:<br>
&gt; &gt; &nbsp;I think it&#39;s best that we let David Ulevitch and the crew @ OpenDNS make<br>
&gt; &gt; &nbsp;the money that is to be made off this. He&#39;s doing good while doing well.<br>
&gt;<br>
&gt; Why shouldn&#39;t anyone be able to &quot;make the money&quot;? The problem with<br>
&gt; that post wasn&#39;t that he was advocating law breaking, it was that it&#39;s<br>
&gt; a marketing missive and inconsistent with community norms, IMHO. That<br>
&gt; doesn&#39;t mean that it&#39;s illegal, and it certainly doesn&#39;t mean it&#39;s ok<br>
&gt; for one &quot;good guy&quot; to be allowed to profit and one unknown not to.<br>
&gt; Setting classes of who can profit from NXDOMAIN data creates<br>
&gt; unfairness in the system and it should be all or none.<br>
<br>
</div>now that our name has been brought into this, i think it&#39;s only fair to<br>
say: the NXDOMAIN data we know about is when a user&#39;s resolver asks our<br>
recursive servers for a record and NXDOMAIN is the end result of what<br>
our resolvers discover.<br>
<br>
at that point, we optionally point you at a lander page w/ search results<br>
and ads and all that jazz based on the words in the record you [mis-]typed.<br>
note the optionally. if you want, we&#39;ll just return NXDOMAIN. you can<br>
configure this. you can configure it per-ip, per-prefix, etc.<br>
<br>
now, on to what we do or could do with that data:<br>
<br>
we do not sell and have never sold NXDOMAIN data. nor do we register<br>
domains based on NXDOMAIN information. the non-OpenDNS company who sees<br>
the original request that produced the NXDOMAIN that failed (which may<br>
or may not even be a valid hostname) is our advertising partner.<br>
<br>
they get that data after we&#39;ve transformed the original request into<br>
their API to send to them as keywords so they may return appropriate and<br>
relevant ads.<br>
<br>
so, to recap:<br>
nope, we don&#39;t sell NXDOMAIN data. we don&#39;t sell any other data either.<br>
yes, some revenue comes from typos/mistakes. you knew that already.<br>
yes, you can even change that behavior and just get NXDOMAIN.<br>
 &nbsp;that means your typos gain us nothing. you get our service for free.<br>
yes, you opt-in to our service in the first place.<br>
yes, we have a privacy policy that says this better than i can.<br>
<div class="Ih2E3d"><br>
&gt; What you really want to look at is privacy policy. Not all of the good<br>
&gt; guys are actually good guys in that respect.<br>
<br>
</div><a href="http://www.opendns.com/privacy/" target="_blank">http://www.opendns.com/privacy/</a><br>
<br>
it looks pretty good to me. i read it before i agreed to employment.<br>
<br>
-- billf &gt;at&lt; <a href="http://opendns.com" target="_blank">opendns.com</a> // opendns network engineering<br>
<br>
p.s. since i rarely if ever post, i have to make the shameless, shameless<br>
 &nbsp; &nbsp; plug: &lt;<a href="mailto:peering@opendns.com">peering@opendns.com</a>&gt;. we&#39;re in peeringdb too.<br>
<br>
<br>
<br>
</blockquote></div><br>

------=_Part_23713_20087574.1206720769588--


home help back first fref pref prev next nref lref last post