On Monday, July 7, 2025 1:54:41 AM CEST Bagas Sanjaya wrote:
> That override won't persist across reboots, though, in my case (I'm using
> NetworkManager).
>
> Thanks.
...--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this
On Sun, Jul 06, 2025 at 08:10:58PM +0200, Bjørn Mork via bind-users wrote:
> Bagas Sanjaya writes:
>
> > Here in my case, I was expecting BIND to listen to 127.0.0.53 as
> > separate address, just like in similar applications (systemd-resolved,
> > dnsdist, etc).
>
> You do need to add the addre
Bagas Sanjaya writes:
> Here in my case, I was expecting BIND to listen to 127.0.0.53 as
> separate address, just like in similar applications (systemd-resolved,
> dnsdist, etc).
You do need to add the address to an interface, but you don't need to
add a new dummy interface. This will make your
New-Subject: host vs subnet routes
Old-Subject: BIND doesn't listen to other loopback addresses
On 7/6/25 1:02 AM, Ondřej Surý wrote:
The IPv4 loopback is actually quite weird in this regard that
127.0.0.1/8 is assigned by everything in 127/8 automagically works
without explicit address assig
On 7/6/25 12:48, Michael De Roover wrote:
On Sunday, July 6, 2025 4:40:37 AM CEST Michael De Roover wrote:
Omit 127.0.0.53, like so:
options {
listen-on {
192.168.0.155;
};
};
Works fine for me using IP addresses 192.168.10.{4-6}, on Alpine edge. You
can keep v6
On Sunday, July 6, 2025 2:34:58 AM CEST Bagas Sanjaya wrote:
> Hi,
>
> I notice BIND's address binding behavior (bug?). I'm running BIND from
> git (9.21.10-dev (Development Release) ).
>
> My named.conf specifies listen-address to both loopback and WiFi devices:
>
> ```
> options {
> ...
6 matches
Mail list logo
