Re: can't resolve some addresses

Except that, in this case, there is nothing wrong with putting RD in a
query to an authoritive server that is authoritative for the zone you
are querying.  The mozilla server doesn't need to recurse; its got the
authority data.

The bug is in the mozilla server for refusing the query, even though it
was authoritative for the answer.  Turning off recursion should only be
cause queries to be refused if recursion was necessary; in this case,
recursion wasn't necessary.

		--Dean



On Sun, 5 Apr 2009, Jeff King wrote:

> On Mon, Apr 06, 2009 at 06:17:00AM +0300, Alex Efros wrote:
> 
> > Correct me if I wrong, it looks like dnscache behaviour was changed at
> > some version (I'm using it from ~2001 with same configuration including
> > FORWARDONLY=0) and now to resolve using root dns servers instead of my
> > ISP's dns servers I have to delete FORWARDONLY instead of setting it to 0?
> 
> Nope. FORWARDONLY was introduced in djbdns-1.02, and has always had that
> behavior. The relevant line is:
> 
>   $ grep -A1 FORWARDONLY dnscache.c
>   if (env_get("FORWARDONLY"))
>     query_forwardonly();
> 
> which does not actually look at the value, only whether it is set.
> 
> It looks like you have been sending queries with the RD bit set for
> years. If you did not put your ISP's dns servers into "@", then you have
> been making recursive queries of random authoritative servers.
> 
> -Peff
> 
> 

-- 
Av8 Internet   Prepared to pay a premium for better service?
www.av8.net         faster, more reliable, better service
617 344 9000