Re: Very long delays, is it just djbdns?

(* Reply to /dev/null'd *)

On 15/11/10 21:40, Hauke Lampe wrote:

> I think it has to do with dnscache resolving all glue before proceeding
> to the next level. The log shows a lot of outgoing queries and several
> "input/output errors" as well as "protocol errors".

Initially I was getting fairly fast lookups, but flushing the cache then
running the query again shows the long lookup behaviour.

# svc -t /service/dnscache

# time dnsqr ptr 4.5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.e.3.0.1.9.0.f.1.7.7.4.0.1.0.0.2.ip6.arpa
12 4.5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.e.3.0.1.9.0.f.1.7.7.4.0.1.0.0.2.ip6.arpa:
timed out

real    0m59.117s
user    0m0.000s
sys     0m0.000s

# time dnsqr ptr 4.5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.e.3.0.1.9.0.f.1.7.7.4.0.1.0.0.2.ip6.arpa
12 4.5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.e.3.0.1.9.0.f.1.7.7.4.0.1.0.0.2.ip6.arpa:
90 bytes, 1+0+0+0 records, response, authoritative, nxdomain
query: 12 4.5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.e.3.0.1.9.0.f.1.7.7.4.0.1.0.0.2.ip6.arpa

real    0m15.066s
user    0m0.000s
sys     0m0.000s

# time dnsqr ptr 4.5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.e.3.0.1.9.0.f.1.7.7.4.0.1.0.0.2.ip6.arpa
12 4.5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.e.3.0.1.9.0.f.1.7.7.4.0.1.0.0.2.ip6.arpa:
90 bytes, 1+0+0+0 records, response, authoritative, nxdomain
query: 12 4.5.3.2.0.0.0.0.0.0.0.0.0.0.0.0.e.3.0.1.9.0.f.1.7.7.4.0.1.0.0.2.ip6.arpa

real    0m0.001s
user    0m0.000s
sys     0m0.000s



-- 
Regards,
  Daryl Tester

"It's bad enough to have two heads, but it's worse when one's unoccupied."
  -- Scatterbrain, "I'm with Stupid."