Re: BIND doesn't listen to other loopback addresses

Bagas Sanjaya writes: > Yet, the change **does not** persist on reboot (IOW, that 127.0.0.53 address > is gone or back to defaults). Hence, I have to add dummy interface. No network configuration is persistent unless you make it so. I assumed that was obvious. Bjørn -- Visit https://lists.is

Re: BIND doesn't listen to other loopback addresses

Hi, I do not know if you are using Redhat EL 9 or not but I found this article from Redhat that seems to describe how one might manage the loopback interface with NetworkManager: https://access.redhat.com/solutions/2108251 On Mon, Jul 7, 2025 at 4:48 AM Bagas Sanjaya wrote: > > On Mon, Jul 07,

Re: BIND doesn't listen to other loopback addresses

On Mon, Jul 07, 2025 at 03:28:57AM +0200, Michael De Roover wrote: > 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. > > ... That's not what I mean. As I iterate: I wo

Re: BIND doesn't listen to other loopback addresses

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

Re: BIND doesn't listen to other loopback addresses

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

Re: BIND doesn't listen to other loopback addresses

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

Re: BIND doesn't listen to other loopback addresses

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

Re: BIND doesn't listen to other loopback addresses

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 { > ...

Re: BIND doesn't listen to other loopback addresses

On 7/6/25 12:30, Greg Choules wrote: https://bind9.readthedocs.io/en/stable/reference.html#namedconf- statement-automatic-interface-scan Note the phrase "...and supported by the operating syst

Re: BIND doesn't listen to other loopback addresses

On 7/6/25 13:02, Ondřej Surý wrote: On 6. 7. 2025, at 2:35, Bagas Sanjaya wrote: It seems like BIND only listen to addresses that are assigned to existing network devices, no? The thread got little bit muddled, but basically the answer is: yes, that’s right. The IPv4 loopback is actually qu

Re: BIND doesn't listen to other loopback addresses

> On 6. 7. 2025, at 2:35, Bagas Sanjaya wrote: > > It seems like BIND only listen to addresses that are assigned to existing > network devices, no? The thread got little bit muddled, but basically the answer is: yes, that’s right. The IPv4 loopback is actually quite weird in this regard that 1

Re: BIND doesn't listen to other loopback addresses

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 none. One of the more basic op

Re: BIND doesn't listen to other loopback addresses

On Sunday, July 6, 2025 7:21:19 AM CEST Bagas Sanjaya wrote: > On Sun, Jul 06, 2025 at 11:52:35AM +1000, Mark Andrews wrote: > > Listen-on is an acl. The interface table is scanned for matches which are > > then bound to. This is documented behaviour. > in ARM? Common practice really. Don't consi

Re: BIND doesn't listen to other loopback addresses

https://bind9.readthedocs.io/en/stable/reference.html#namedconf-statement-automatic-interface-scan Note the phrase "...and supported by the operating system...". Linux capabilities must also be enabled (i.e. not *disabled* at build time) for BIND to be able to keep scanning as addresses come and g

Re: BIND doesn't listen to other loopback addresses

On Sun, Jul 06, 2025 at 11:52:35AM +1000, Mark Andrews wrote: > Listen-on is an acl. The interface table is scanned for matches which are > then bound to. This is documented behaviour. in ARM? -- An old man doll... just what I always wanted! - Clara signature.asc Description: PGP signature

Re: BIND doesn't listen to other loopback addresses

On Sunday, July 6, 2025 2:34:58 AM CEST Bagas Sanjaya wrote: > options { > ... > listen-on-v6 { none; }; > listen-on { 127.0.0.53; 192.168.0.155; }; > ... > }; Omit 127.0.0.53, like so: options { listen-on { 192.168.0.155; }; }; Works fine

Re: BIND doesn't listen to other loopback addresses

Listen-on is an acl. The interface table is scanned for matches which are then bound to. This is documented behaviour. -- Mark Andrews > On 6 Jul 2025, at 10:35, Bagas Sanjaya wrote: > > Hi, > > I notice BIND's address binding behavior (bug?). I'm running BIND from > git (9.21.10-dev (Deve

BIND doesn't listen to other loopback addresses

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 { ... listen-on-v6 { none; }; listen-on { 127.0.0.53; 192.168.0.155;