On Sat, 6 Aug 2011, Alan Gutierrez wrote:
It used to be the case that I could flush the unbound cache and then resolve a
name immediately. Now there is a long delay before I start to get results. It
is especially bad on Fedora 15 running in VirtualBox on OS X Lion, but I'm also
seeing it slow down on Fedora 15 at EC2. I updated root.hints, but that didn't
seem to help. I can't make much sense of the debugging logging output. A couple
weeks ago, flushing cache or restarting, you might notice a light delay on the
first lookup, but now it takes a few minutes to get results other than timeouts.
server:
verbosity: 2
num-threads: 1
interface: 127.0.0.1
do-ip4: yes
do-ip6: no
do-udp: yes
do-tcp: no
Why do you have do-tcp set to no? That will cause problems on large dnssec
replies that get
truncated.
use-caps-for-id: yes
You can try disabling this, some servers don't do 0x20 properly and it might be
causing delays.
Paul
_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
