s...@stofa.dk said:
> It is bind 9.16.6, built from ports on FreeBSD 11.3.
Same server combination here but different error.
Aug 27 01:36:25 chuck named[11975]: resolver.c:5125:
INSIST(dns_name_issubdomain(>name, >domain)) failed, back trace
Aug 27 01:36:25 chuck named[11975]: #0 0x43ba00 in
ond...@isc.org said:
> please see release notes:
> https://downloads.isc.org/isc/bind9/9.16.3/RELEASE-NOTES-bind-9.16.3.html
Thank you!
Time to check my eyes (and renew my google search engine membership) since I
should have been able to find that myself.
--Ingeborg
--
Ingeborg Ă˜strem
FreeBSD 11.3-RELEASE-p3
This morning I upgraded from BIND 9.14.11 to 9.16.3 via FreeBSD ports.
Then I realize that my slave server no longer transfer zones from the master.
The zone transfers worked as expected before the upgrade.
There are no error messages. The slave receives notifies from
ond...@isc.org said:
> perhaps you can try running BIND by hand and see why it crashes on the
> console?
Thank you for nudging me in the right direction. I ran named in the foreground
with -g and could finally see the error:
error short read /dev/urandom: Resource temporarily unavailable
FreeBSD 11.2
Bind 9.12.3-P1
I have a server which runs several nameservers, each in its own chroot with
its own assigned IP-address.
They run like this:
/usr/local/sbin/named -4 -t /resolver -u bind -c /etc/namedb/named.conf
In named.conf:
statistics-channels {
inet port 5 allow
I want to upgrade to BIND 9.11.2
I have an anycast cluster and want to pre-set the server cookie string with
option cookie-secret.
My problem is that named-checkconf complains over the length of the
cookie-secret regardless how I set cookie-secret and cookie-algorithm:
options {
...
6 matches
Mail list logo