You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zone files:
foo.com.zone.signed is DNSSEC signed with a record for a.bar (A record or anything)
bar.foo.com.zone doesn't exist (but it's in nsd.conf shown above)
Steps:
Startup NSD
touch foo.com.zone.signed
reload NSD
nsd.log will say:
[2024-10-02 07:19:58.691] nsd[962739]: info: control cmd: reload
[2024-10-02 07:19:58.845] nsd[962752]: error: handle_reload_cmd: reload closed cmd channel
[2024-10-02 07:19:58.845] nsd[962752]: warning: Reload process 962740 failed, continuing with old database
core dump says SIGSEGV in rbtree_find_less_equal
The text was updated successfully, but these errors were encountered:
As reported on nsd-users.
Reproducible seg fault with a DNSSEC signed zone and overlapping config. Running NSD 4.10.1. Here's how to reproduce.
2 zones in
nsd.conf
:Zone files:
foo.com.zone.signed is DNSSEC signed with a record for a.bar (A record or anything)
bar.foo.com.zone doesn't exist (but it's in nsd.conf shown above)
Steps:
nsd.log will say:
core dump says SIGSEGV in rbtree_find_less_equal
The text was updated successfully, but these errors were encountered: