BIND doesn't listen to other loopback addresses

[Mark Andrews]

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 <bagasdotme at gmail.com> wrote:
> 
> Hi,
> 
> I notice BIND's address binding behavior (bug?). I'm running BIND from
> git (9.21.10-dev (Development Release) <id:3719cf5>).
> 
> 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; };
>    ...
> };
> ```
> 
> Starting the instance, I see that BIND only listens to WiFi address in the
> journal:
> 
> ```
> ...
> Jul 06 06:36:52 archie.me named[554]: listening on IPv4 interface wlp2s0, 192.168.0.155#53
> ...
> 
> ```
> 
> I have to add dummy interface:
> 
> ```
> $ nmcli connection add type dummy ifname bind53 ipv4.method manual ipv4.addresses 127.0.0.53/32 ipv4.method disabled
> ```
> 
> Restarting BIND, the journal shows that BIND listens to both addresses:
> 
> ```
> ...
> Jul 06 07:00:42 archie.me named[4906]: listening on IPv4 interface wlp2s0, 192.168.0.155#53
> Jul 06 07:00:42 archie.me named[4906]: listening on IPv4 interface bind53, 127.0.0.53#53
> ...
> ```
> 
> It seems like BIND only listen to addresses that are assigned to existing
> network devices, no?
> 
> Thanks.
> 
> --
> An old man doll... just what I always wanted! - Clara
> --
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
> 
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
> <signature.asc>