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 none. One of the more basic options that's expected to be
>> stable across all distributions regardless.
> 
> FWIW, 127.0.0.53 is allocated by systemd-resolved. In a context of BIND, you
> neither need it (BIND is already acting as a DNS server), nor even want it
> (due to conflicts when binding to the network interfaces). Chances are that
> either something in your system brought 127.0.0.53 in there by script, or that
> some (misguided) guide made you put that in there. When in doubt, that address
> does not belong there, and that's probably all there is to it.
> 

I already masked systemd-resolved.service (I don't have any use case for 
it, though). Instead, I create dummy interface with 127.0.0.53 address. 
Again that's my personal taste.

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
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users