Hi Chris, Thanks for reporting! I'll look into this.
- Jeroen On Wed, 2024-10-02 at 14:57 +0000, Chris LaVallee via nsd-users wrote: > > Hi, > > > I found a reproducible seg fault with a DNSSEC signed zone and > overlapping config. I'm running NSD 4.10.1. Here's how to reproduce. > > > 2 zones in nsd.conf: > > > zone: > name: "foo.com." > zonefile: "/zones/foo.com.zone.signed" > > > zone: > name: "bar.foo.com." > zonefile: "/zones/bar.foo.com.zone" > > > > > 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: > 1) Startup NSD > 2) touch foo.com.zone.signed > 3) 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 > > > > > Chris LaVallee > Edgio (formally EdgeCast Networks) > > > > > _______________________________________________ > nsd-users mailing list > nsd-users@lists.nlnetlabs.nl > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users _______________________________________________ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
