Bugzilla – Bug 287
Unbound dies when removing nonexistent local-data with unbound-control
Last modified: 2009-12-15 12:35:23 CET
Created attachment 127 [details]
unbound-control stdout/stderr output
Setup: unbound 1.4.0, ldns 1.6.2, no threads, no libevent, and no python support, running under gentoo linux, x86. I tested this with a default config, only adding a transparent local-zone 'tomhendrikx.nl' to the server, without any local-data in it.
When issuing "unbound-control local_data_remove test.tomhendrikx.nl", unbound crashes while trying to remove the nonexistent local-data. I can reliably reproduce the crash every time, directly after restarting unbound.
In attachments the output from unbound and unbound-control with debug enabled.
Created attachment 128 [details]
unbound syslog output
Hi Tom, Thanks for the report, I reproduced and fixed the bug in svn r1926.
Thanks for the debug output. Note well that the malloc-debugging you enabled there likely slows down unbound a lot and so it probably not suitable for a production environment.
Best regards, Wouter
I'm not if this is the same issue (bug and commit message don't much about the actual issue), but I found another trivial typo in the 'unbound-control local_data' command, tested against trunk (r1930). The following command also crashes unbound:
unbound-control local_data 220.127.116.11.in-addr.arpa. IN PTR .tomhendrikx.nl
I can add some debug output again when needed, but this one is also easily reproduced here.
This one turns out to be an error in ldns. Fixed it there, (updated tarball inside the unbound svn repo), and it now gives syntax error for starting a domain name with a dot.
Please report more of these errors if you can generate them :-)
Closing bug, thanks for filing it.