Hi Guys,
Is anyone else experiencing intermittent DNS issues with
bodybuilding.com?
With verbosity set to 99, here's what I see in our logs:
Hi Guys,
Is anyone else experiencing intermittent DNS issues with
bodybuilding.com?
With verbosity set to 99, here's what I see in our logs:
Could it be that the RTT is too high? USEFUL_SERVER_TOP_TIMEOUT defaults
to 120000.
Also, there's 5 servers returned. Somehow it doesn't try the 5th?
Jan 06 12:59:37 unbound[16172:1] debug: Bad choices, trying to get more
choice
Jan 06 12:59:37 unbound[16172:1] debug: querying for next missing target
Jan 06 12:59:37 unbound[16172:1] debug: out of query targets --
returning
Regards,
Haw
Forgot to mention, we're running Unbound 1.4.1. my.commbank.com.au is
another domain our users are having problems with.
Output from unbound-host:
Hi Haw,
For commbank, I see one thing:
dig @140.168.70.10 my.commbank.com.au. AAAA
gives timeouts, but type A or MX works fine.
This should still work with unbound.
For me unbound-host resolves both names fine, with the svn trunk and
also unbound-1.4.1 versions. Can you run unbound-host like you did and
send me the full debug output (offlist, gzipped?)
In your debug output it says all targets are bad choices, this is
usually done with servers that are lame.
Same for the other domain, if you could send me a debug log, I could
tell more. Looks like unbound detected some sort of lame servers.
Best regards,
Wouter
Hi,
Results of debugging offlist, the fix is in svn and Haw reports the
troubles seems to be gone.
Best regards,
Wouter
Hi Sergey,
svn r1953 contains the fix.
# svn diff -r 1952:1953 > patch.diff
# patch -p0 < patch.diff
(except for the changelog which probably conflicts).
Best regards,
Wouter
Hi Guys,