Re: bind crashes with assertion, maybe due to many ephemeral network devices?

lease do not feel obligated to reply outside your normal working hours. On 10. 3. 2025, at 21:19, Erich Eckner wrote: Hi, I'm running bind version 9.20.6 on artix linux (an arch linux derivate without systemd) with a pretty standard config: # named -V BIND 9.20.6 (Stable Releas

bind crashes with assertion, maybe due to many ephemeral network devices?

Hi, I'm running bind version 9.20.6 on artix linux (an arch linux derivate without systemd) with a pretty standard config: # named -V BIND 9.20.6 (Stable Release) running on Linux x86_64 6.13.5-artix1-1 #1 SMP PREEMPT_DYNAMIC Fri, 28 Feb 2025 10:18:15 + built by make with '--prefix=/usr

Re: parental-agents clause - IP address only ?

Hi, On Mon, 5 Dec 2022, Matthijs Mekking wrote: 'parental-agents' work the same as 'primaries'. It only supports addresses. Listing them as domain names would technically be possible to implement, but it requires an authoritative server to act as an resolver. Adding resolver code to the pa

Re: host your subdomain on your own ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 13 Nov 2021, Reindl Harald wrote: Am 12.11.21 um 18:55 schrieb lejeczek via bind-users: On 12/11/2021 17:14, Reindl Harald wrote: wouldn't it be easier to setup two different subdomains in which case you don't need delegation at all - yo

Re: BIND 9.16.17-snapshot - testers needed - recursive performance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I switched to the 9.16.17 release candidate yesterday and so far, it runs well on my 6 very-low traffic dns servers (one of which is also authoritative). Only thing, I noticed, is, that it uses more memory than 9.16.16 on the weakest of my

Re: BIND 9.16.17-snapshot - testers needed - recursive performance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 25 May 2021, Ondřej Surý wrote: Hi, Hi Ondrej, we merged a change that substantially reduces a contention between threads and improves the recursive performance in 9.16 branch quite significantly. After the change, the 9.16 branch pe

AXFR rejected

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I upgraded from bind 9.16.11 to 9.16.12 (on arch linux) and suddenly, AXFR transfers were denied: 19-Feb-2021 13:56:01.276 client @0x7f37c8015028 127.0.0.1#57139: TCP request 19-Feb-2021 13:56:01.276 client @0x7f37c8015028 127.0.0.1#57139: u

rpz depending on query type

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I'm running bind as a recursive dns server. I wonder, if it's possible to modify responses via rpz for some query type only - e.g.: I want to return NODATA for "example.com ", but the real answer for "example.com A" (and all other record

Re: Steps to reload zone files automatically?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 1 Jul 2020, Harshith Mulky wrote: Hello Hi, Is there an automatic way we could use reloading the zone files rather than using rndc reload or named restart? Shouldn't the design be, that: Whoever changes the zone file, runs "rndc rel

Re: DoH plugin for BIND

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I assume, the (on-topic) discussion so far was about the serving part of bind. (Correct me, if I'm wrong) Will there be client-side DoT/DoH support in bind, too? E.g. will my recursive (or forwarding) resolver be able to resolve upstream dn

Re: AW: Debian/Ubuntu: Why was the service renamed from bind9 to named?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 15 Apr 2020, Klaus Darilion wrote: -Ursprüngliche Nachricht- Von: bind-users Im Auftrag von Reindl Harald Gesendet: Mittwoch, 15. April 2020 09:05 An: bind-users@lists.isc.org Betreff: Re: Debian/Ubuntu: Why was the service rename

Re: bind as "reverse-proxy"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 26 Feb 2020, Matus UHLAR - fantomas wrote: On 26.02.20 15:28, Erich Eckner wrote: is it possible to set up a zone in bind similar to a http(s) reverse proxy: No. DNS is very far from proxying. 1. The server appears authoritative to

bind as "reverse-proxy"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, is it possible to set up a zone in bind similar to a http(s) reverse proxy: 1. The server appears authoritative to clients (the consulted server is indeed authoritative). 2. Each request is passed on to the other server (or served from ca

Re: .onion and dnssec

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 12 Nov 2019, Tony Finch wrote: Erich Eckner wrote: I have also a hard time, generating some useful debug output - setting `-d 9` does not give additional information in the system log. You might find it is being written to the file

Re: .onion and dnssec

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Tony, On Mon, 11 Nov 2019, Tony Finch wrote: Erich Eckner wrote: However, I encounter the issue here: https://lists.isc.org/mailman/htdig/bind-users/2011-November/085536.html If you are running 9.14 (or newer) you can use the validate

.onion and dnssec

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I'm running a recursive bind (root hint, several master zones for opennic tlds) and would like to extend it by resolving .onion addresses through my tor node. Naively, I tried to add this to my config file: zone "onion" IN { type forwa

Re: per-zone query-source on recursive resolver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, On Mon, 28 Oct 2019, Tony Finch wrote: Erich Eckner wrote: RPZ rewrites responses as they are going out of your nameserver, so you can't use RPZ to change the way the nameserver's resolver works (because the resolver depends o

per-zone query-source on recursive resolver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I'm running bind as a recursive resolver. This box also has a vpn tunnel to another network (not mine) with split-horizon dns (internal clients see different NS entries than external clients; those in turn resolve different addresses). I wou

make bind prefer DoT for recursion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I am running a recursive resolver for my local network and was wondering whether it is possible (and if so: how) to make it resolve via DNS-over-TLS if that's available on the authoritative name servers. Setting up stunnel like for stub res

forward all but ANY requests

Hi, I'm running a bind9 name server (9.13.4 on debian) which forwards some zone (onion.) to tor's name server. Unfortunately, tor's name server only answers A and requests, but not e.g. ANY requests. 192.168.1.3 is running the tor dns, 192.168.1.13 is running bind9 forwarding to 192.168.1.3: