On Tue, Mar 22, 2011 at 11:08:32AM +0000, Russell Hafter - Lists wrote: > In article <20110322105125.ga15...@rjek.com>, Rob Kendrick > <r...@netsurf-browser.org> wrote: > > > On Tue, Mar 22, 2011 at 10:25:56AM +0000, Tim Hill wrote: > > > > As a side note, this also reveals that OpenDNS may not > > > be a good idea with NetSurf because OpenDNS error pages > > > use javascript and the <noscript> section doesn't work > > > here either. > > > Does OpenDNS not just return NXDOMAIN when a domain does > > not exist? If it returns a rewrite to another page on > > error, then that's an excellent reason to not use it. > > OpenDNS diverts you, using JS, to its own search engine > (which I have heard, is done by Yahoo).
Oh dear. This means that their DNS servers lie to you about what exists and what does not exist. This breaks a startling number of things, as discovered by Verisign when they tried to do it for .com, causing them to hurriedly backtrack on it. Anyway, this isn't related to NetSurf, or the problem reported (which is an accidental server misconfiguration, not a DNS fault.) B.
