Re: bind 9.16.6 on FreeBSD - Assert

> On 1 Sep 2020, at 19:48, Søren Andersen wrote: > > hmm.. I think you hit this bug right here: > https://gitlab.isc.org/isc-projects/bind9/-/issues/2104 Looks like that. I compiled bind with debug symbols and it crashed again. No way to append this to your bug report, it’s closed. Borja

Re: Upgrading from 9.14.12 to 9.16.4 - with existing DNSSEC zones

Do you go to your mechanic and not take the car when you have a problem you don’t understand with the car? BIND 9.16.4 should be a drop in replacement for 9.14.12. As you are seeing issues you will need to supply more details like the name of the zone so people can actually try and figure out

Re: No response from localhost with "allow-query { any; };"

tcp queries are being answered, but udp queries receive no response. This is independent of client location (local, remote). A ktrace shows 8 bytes are written on fd 89, the 8 bytes read on fd 88. The next read gets an errno 35 (see below). clueless, Axel root@ns5:/var/log # uname -a FreeBSD ns

Re: bind 9.16.6 on FreeBSD - Assert

hmm.. I think you hit this bug right here: https://gitlab.isc.org/isc-projects/bind9/-/issues/2104 /Søren From: bind-users on behalf of Borja Marcos Sent: Tuesday, September 1, 2020 17:12 To: bind-users@lists.isc.org Subject: bind 9.16.6 on FreeBSD - Assert [

bind 9.16.6 on FreeBSD - Assert

Hi, I had a named process aborting with an assert. <26>1 2020-08-27T15:52:04.00+00:00 host named 6520 - - rbt.c:2355: REQUIRE(newbits <= rbt->maxhashbits) failed, back trace <26>1 2020-08-27T15:52:04.00+00:00 host named 6520 - - #0 0x43d260 in ?? <26>1 2020-08-27T15:52:04.00+00:00 h

Re: No response from localhost with "allow-query { any; };"

> Am 01.09.2020 um 16:57 schrieb Petr Menšík : > > Please include any listen-on { ... } and listen-on-v6 { ... } clauses. > > It seems any of 127.0.0.1; ::1; nor localhost; is listed in them. > Because it is not listening on localhost socket, it would not answer any > queries. > Voilà:

Upgrading from 9.14.12 to 9.16.4 - with existing DNSSEC zones

I am using DNSSEC for more than 5 years now (never had a problem so far), but after upgrading to the latest bind-9.16.4 the verification fails using Verisign's DNSSEC Validator. I reverted back to 9.14.12 and everything works as expected. First I started upgrading my secondary DNS-Server (p

Re: No response from localhost with "allow-query { any; };"

Please include any listen-on { ... } and listen-on-v6 { ... } clauses. It seems any of 127.0.0.1; ::1; nor localhost; is listed in them. Because it is not listening on localhost socket, it would not answer any queries. If the server should listen on all interfaces, just use: listen-on { any; };

Re: No response from localhost with "allow-query { any; };"

Thanks for answering: root@ns5:/ # dig NS lrau.net @91.216.35.21 ; <<>> DiG 9.16.5 <<>> NS lrau.net @91.216.35.21 ;; global options: +cmd ;; connection timed out; no servers could be reached root@ns5:/ # dig NS lrau.net @localhost ; <<>> DiG 9.16.5 <<>> NS lrau.net @localhost ;; global options:

Re: No response from localhost with "allow-query { any; };"

Thanks for your answer! > Am 01.09.2020 um 16:18 schrieb Warren Kumari : > > The output you included doesn't really show very much, other than that nc > connect to port 53. > > I'd suggest: > dig ns5.lrau.net @localhost > dig ns5.lrau.net @127.0.0.1

Re: No response from localhost with "allow-query { any; };"

What is 'localhost'? The output you included doesn't really show very much, other than that nc connect to port 53. I'd suggest: dig ns5.lrau.net @localhost dig ns5.lrau.net @127.0.0.1 dig ns5.lrau.net @::1 Also, have a look in /etc/hosts and make sure that you have something like: 127.0.0.1 loca

Re: No response from localhost with "allow-query { any; };"

Hi Axel, the `nc` commands you used for testing neither proves that it’s that specific `named` listening on that port nor DNS daemon at all. FWIW it could be a dummy UDP/TCP server and you would not know. First you need to use a tool from your operating system to check what is listening on those

No response from localhost with "allow-query { any; };"

Hi! this is a new server, which answers external queries, sends notifies and pushes axfrs. It does not answer any query from localhost nor shows any notifies from master in the logs. From local: root@ns5:/ # nc -v localhost 53 Connection to localhost 53 port [tcp/domain] succeeded! ^C root@ns5:

Re: rpmbuild problem with 9.11.22 on Centos

Hi Matthew, it would also help to make setting flags not mandatory. Changing it to: %{?set_build_flags} Would use it whenever the macro is supported and expand it to empty on legacy systems. Another possibility would be skipping epel dependency: %if 0%{?rhel} && 0%{?rhel} <= 7 export CFLAGS="%o