FS#40342 - [bind] named crashes when "type forward" used for a zone.
Attached to Project:
Community Packages
Opened by AMM (amish) - Tuesday, 13 May 2014, 04:22 GMT
Last edited by Sébastien Luttringer (seblu) - Thursday, 15 May 2014, 22:29 GMT
Opened by AMM (amish) - Tuesday, 13 May 2014, 04:22 GMT
Last edited by Sébastien Luttringer (seblu) - Thursday, 15 May 2014, 22:29 GMT
|
Details
Description:
I have this line in named.conf zone "multi.uribl.com" { type forward; }; I use OpenDNS forwarders in main options but I wanted "exception" for "multi.uribl.com". So I had added above 3 lines. This worked perfect in 9.9.5.W1-2 but after updating to 9.10.0.P1-1 named started crashing immediately on start. Removing/commenting lines resolves issue but "exception" is lost. Additional info: * package version(s) named-9.10.0.P1-1 * config and/or log files etc. Backtrace log is attached. Steps to reproduce: Add these lines in named.conf and restart named options { ... ... forward first; forwarders { 208.67.222.222 ; 208.67.220.220 ; }; //OpenDNS } zone "multi.uribl.com" { type forward; }; |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Thursday, 15 May 2014, 22:29 GMT
Reason for closing: Deferred
Additional comments about closing: Workaround is provided. Will be fixed in next upstream release.
Thursday, 15 May 2014, 22:29 GMT
Reason for closing: Deferred
Additional comments about closing: Workaround is provided. Will be fixed in next upstream release.
zone "multi.uribl.com" {
type forward;
forwarders { };
};
But named should not have crashed even if forwarders line is missing.
However there is another similar looking crash that soon follows which is reported at bug#40304
Downgraded back to 9.9.5.W1-2
Thank you for the recipe to reproduce this issue. A fix for the problem is in review upstream. The upstream ticket number is ISC-Bugs #35979.
As a workaround, try this:
zone "multi.uribl.com" {
type forward;
forwarders {};
};
If you mail <bind9-bugs@isc.org> reporting this problem, you'll get email to keep track of this bug, and we'll send you a patch to try.
Anyway, I suppose this bug can be closed.
The crash has been fixed and the fix will be in a release soon (after it's been reviewed, merged, etc.). If you want the patch before that, please mail us. Thank you again for getting back to us with information necessary for debugging this issue.
Thanks for quick patch and reply.