This is a discussion on External resolution timeouts within the Bind Users forums, part of the DNS and Related Forums category; Hey everybody! I'm having weird timeout issues when resolving names for which my local nameserver is not authoritative. If ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hey everybody! I'm having weird timeout issues when resolving names for which my local nameserver is not authoritative. If I try to resolve an external name using dig or nslookup, my query will almost always fail the first time. However, it will succeed either on the first or second successive try. Debugging output on tracelevel 3 shows lots of: resquery 0x810fb90 (fctx 0x80fb378): send resquery 0x810fb90 (fctx 0x80fb378): sent resquery 0x810fb90 (fctx 0x80fb378): senddone fctx 0x80f0e90: timeout fctx 0x80f0e90: try fctx 0x80f0e90: query resquery 0x810fe08 (fctx 0x80f0e90): send resquery 0x810fe08 (fctx 0x80f0e90): sent resquery 0x810fe08 (fctx 0x80f0e90): senddone fctx 0x80eb8d8: timeout fctx 0x80eb8d8: try fctx 0x80eb8d8: query resquery 0x8110080 (fctx 0x80eb8d8): send fctx 0x80eb8d8: too many timeouts, disabling EDNS0 resquery 0x8110080 (fctx 0x80eb8d8): sent fctx 0x80edb70: timeout I'm running BIND 9.2.2rc1 on Linux 2.4.20. Any ideas, hints, or nudges in the right direction would be appreciated. Thanks! |