freebs 10.3 bug in bind 9.9.9 May 22 22:03:21 servis named[40688]: rbt.c:1975: INSIST(sibling != ((void *)0)) failed, back trace May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: rbt.c:1975: INSIST(sibling != ((void *)0)) failed, back trace May 22 22:03:21 servis kernel: pid 40688 (named), uid 53: exited on signal 6 May 22 22:03:21 servis named[40688]: #0 0x4175ad in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #0 0x4175ad in ?? May 22 22:03:21 servis named[40688]: #1 0x5aa52a in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #1 0x5aa52a in ?? May 22 22:03:21 servis named[40688]: #2 0x4b2f8e in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #2 0x4b2f8e in ?? May 22 22:03:21 servis named[40688]: #3 0x4be2fd in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #3 0x4be2fd in ?? May 22 22:03:21 servis named[40688]: #4 0x4bd91a in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #4 0x4bd91a in ?? May 22 22:03:21 servis named[40688]: #5 0x4ba075 in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #5 0x4ba075 in ?? May 22 22:03:21 servis named[40688]: #6 0x5262d2 in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #6 0x5262d2 in ?? May 22 22:03:21 servis named[40688]: #7 0x5c8d53 in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #7 0x5c8d53 in ?? May 22 22:03:21 servis named[40688]: #8 0x801851855 in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #8 0x801851855 in ?? May 22 22:03:21 servis named[40688]: #9 0x0 in ?? May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: #9 0x0 in ?? May 22 22:03:21 servis named[40688]: exiting (due to assertion failure) May 22 22:03:21 servis kernel: May 22 22:03:21 servis named[40688]: exiting (due to assertion failure)
This looks like a BIND problem non related to FreeBSD. Have you reported it to the ISC ? https://www.isc.org/community/report-bug/
This should have been fixed by last update.