North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Hey, SiteFinder is back, again...

  • From: Eliot Lear
  • Date: Mon Nov 05 02:29:01 2007
  • Authentication-results: ams-dkim-1; [email protected]; dkim=pass (s ig from cisco.com/amsdkim1002 verified; );
  • Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=918; t=1194247645; x=1195111645; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; [email protected]; z=From:=20Eliot=20Lear=20<[email protected]> |Subject:=20Re=3A=20Hey,=20SiteFinder=20is=20back,=20again... |Sender:=20; bh=SaF0p8TLcUF/xEzzSK/o/Kzjj4Kv+DmMED7SAnYgBbU=; b=rLmF+Hs8qM/LYuMZI0+yPjPymgwSrcKXdKWNzm3jJmky65DulOEwwrGQgP1g6HLAh074U1ZR yIciMdqCLZ52zxrEfTDW6i6fAJn7kqTtoytvEjZOkHL4YG80HrXftOii;
Sean,
>>
>> Yes, it sounds like the evil bit.  Why would anyone bother to set it?
>
> Two reasons
>
> 1) By standardizing the process, it removes the excuse for using
> various hacks and duct tape.
>
> 2) Because the villian in Bond movies don't view themselves as evil.
> Google is happy to pre-check the box to install their Toolbar, OpenDNS
> is proud they redirect phishing sites with DNS lookups, Earthlink says it
> improves the customer experience, and so on.

Forgive my skepticism, but what I would envision happening is resolver
stacks adding a switch that would be on by default, and would translate
the response back to NXDOMAIN.  At that point we would be right back
where we started, only after a lengthy debate, an RFC, a bunch of code,
numerous bugs, and a bunch of "I told you sos".

Or put another way: what is a client resolver supposed to do in the face
of this bit?

Eliot