Re: bind on fbsd no longer starting

Hi! > when I try to start bind 9.18.30 from the ports tree, build > for fbsd 14.1p5, I get this error: [...] > 14-Oct-2024 22:14:14.515 compiled with libuv version: 1.49.1 Downgrading libuv to 1.48.0 seems to fix the startup problem. See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282088

bind on fbsd no longer starting

Hi! when I try to start bind 9.18.30 from the ports tree, build for fbsd 14.1p5, I get this error: 14-Oct-2024 21:49:18.566 netmgr/netmgr.c:302:isc__netmgr_create(): fatal error: 14-Oct-2024 21:49:18.566 uv_loop_init failed: no such file or directory 14-Oct-2024 21:49:18.566 exiting (due to fata

Old link in DNSSEC Guide for number of TLDs with DNSSEC

Hi! In https://bind9.readthedocs.io/en/v9.18.19/dnssec-guide.html there's a link to https://stats.research.icann.org/dns/tld_report/ which is no longer valid. New data seems to be here: https://ithi.research.icann.org/ ITHI == idenitifier technologies health indicators how many TL

Is bind 9.18.19 a validating resolver to shield against CVE-2023-42119 ?

Hi! In the light of the recent exim security issues[1,2] I'm trying to find out if bind 9.18.19, if used as resolver, does enough validation to shield exim instances from CVE-2023-42119 ? As details and reproducers for the CVE are not available, this is a more general question. Pointers on where

Re: many log messages with 'already have ede' etc ?

Hi! Mark wrote: > > We do have somewhat extensive logging on our auth DNS servers, > > and currently, we see a load of messages like those: > > > client @0x80357ad60 #5701 ( > 18 (null) > They are debugging messages. Stop running in debug mode. Done, logging is quieter now. Thanks! -- p...@o

many log messages with 'already have ede' etc ?

Hi! We do have somewhat extensive logging on our auth DNS servers, and currently, we see a load of messages like those: client @0x80357ad60 #5701 (#65358: set ede: info-code 18 extra-text (null) What do those messages report and how can I silence those messages ? -- p...@opsec.eu+4

Re: bind 9.18.7, fbsd13.1: crash with signed/signing zone

Hi! > I have a zone definition like this: > > zone "myzone" in { > type master;file "signed/myzone"; Aha, this file path was wrong. Fixed, at least it crashes no longer. -- p...@opsec.eu+49 171 3101372Now what ? -- Visit https://lists.isc.org/mailman/listinfo

bind 9.18.7, fbsd13.1: crash with signed/signing zone

Hello, I have a zone definition like this: zone "myzone" in { type master;file "signed/myzone"; allow-transfer { "myacl"; }; inline-signing yes; dnssec-policy default; }; and starting bind9.18.7 on FreeBSD 13.1 (self-compiled ports version) leads to this crash, according to syslog, see b

bind 9.16.28 vrs. 9.18.2 (on freebsd) resolving foryoudecor.com

Hello, we observed a strange behaviour for the domain foryoudecor.com, when trying to resolve it using bind 9.18.2, using dig -t mx foryoudecor.com The bind log for 9.18.2 says: May 11 12:00:14 ns named[96774]: fetch: foryoudecor.com/MX May 11 12:00:14 ns named[96774]: DNS format error from 61.