BIND 10 #1387: timeout on xfrout when sock path too long
BIND 10 Development
do-not-reply at isc.org
Tue Nov 15 12:40:31 UTC 2011
#1387: timeout on xfrout when sock path too long
-------------------------------------+-------------------------------------
Reporter: jelte | Owner:
Type: defect | Status: new
Priority: major | Milestone: New
Component: Unclassified | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
in this case, it got triggered by the lettuce xfrin test; if the
auth->xfrout domain socket path is too long, you get a timeout when you
try to transfer from bind 10. Looks like auth fires off the request but
doesn't do anything if it fails.
We should probably log a potential problem with the sockpath length, and
return SERVFAIL instead of 'nothing'. Perhaps we need to check if there
are other failure scenario's where one could end up with a timeout instead
of a error response as well.
--
Ticket URL: <http://bind10.isc.org/ticket/1387>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list