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,

Re: BIND doesn't listen to other loopback addresses

. That's not what I mean. As I iterate: I work around this problem by explicitly adding additional IP address to the loopback interface (see my initial post on this thread). Yet, the change **does not** persist on reboot (IOW, that 127.0.0.53 address is gone or back to defaults). Hence, I have

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

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

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

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

D 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; }; >... > }; > ``` > >

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

Re: loopback

On 2/18/20 7:34 AM, Ward, Mike S wrote: Hello all, I have a small problem, and I was wondering if someone could help me.  My bind9 dns gets a query for loopback. I have tried and tried to define the word loopback in the dns as a forward zone with reverse loopkup, but doesn’t seem to take. I

loopback

Hello all, I have a small problem, and I was wondering if someone could help me. My bind9 dns gets a query for loopback. I have tried and tried to define the word loopback in the dns as a forward zone with reverse loopkup, but doesn't seem to take. I have tried to CNAME it using localhost

Re: resolving from loopback is much smooth?

Hi Graham, Thx for your great tip, it seems it fix my problem. Eric On Tue, Jun 7, 2016 at 5:45 PM, Graham Clinch wrote: > Hi Eric, > > > I run bind dns server 9.9 now with around 3000query/s. I recently > > upgrade our server to Fujitsu M10-1 Solaris 10 with bind9.10. > > I feel that the ser

Re: resolving from loopback is much smooth?

Hi Eric, > I run bind dns server 9.9 now with around 3000query/s. I recently > upgrade our server to Fujitsu M10-1 Solaris 10 with bind9.10. > I feel that the server serving bind is not as fast as old one in intel > solaris which was more than 8 years ago. I tried a few test > and found that dig

resolving from loopback is much smooth?

much more smooth thatn dig @IP the zone at the machine. Try dig resolving from loopback: bash-3.2# i=0; while [ $i -lt 20 ]; do i=`expr $i + 1`; /usr/local/bin/dig @ 127.0.0.1 a |grep "Query time"; sleep 1; done ;; Query time: 0 msec ;; Query time: 0 msec ;; Query time: 0 msec ;; Que

答复：Unexpected srrt in loopback

件人：Darcy Kevin (FCA) 发送时间：2014年11月8日(星期六) 05:53收件人：bind-users@lists.isc.org 主　题：RE: Unexpected srrt in loopback font-family: SimSun;panose-1: 2 1 6 0 3 1 1 1 1 1;font-family: SimSun;panose-1: 2 1 6 0 3 1 1 1 1 1;font-family: Calibri;panose-1: 2 15 5 2 2 2 4 3 2 4;font-family: Tahoma;panose

RE: Unexpected srrt in loopback

The network transit time over software loopback should be minimal, but network transit time isn't the only thing which contributes to overall RTT. Sounds like your named process is struggling to keep up with 5000 QPS. Have you looked at the memory, CPU? Are you running with a single threa

Unexpected srrt in loopback

Hi everyone, I try to set up an authentic bind server in the loopback address(127.0.0.1) in our recursive server of our testbed for test reason. When I send a large number of junk queries(5000QPS), the srrt of loopback server in cash is unexpectedly large. Does anyone know the reason? The srrt is

unexpected loopback srrt

Hi everyone, I try to set up an authentic bind server in the loopback address(127.0.0.1) in our recursive server of our testbed for test reason. When I send a large number of junk queries(5000QPS), the srrt of loopback server in cash is unexpectedly large. Does anyone know the reason? The srrt is

Re: Loopback configuration

my personal sites from behind the router by domain name, a > > function that is necessary. I can see the sites by local > > 192.168 > > ip address and port number and others have confirmed they are > > available on the www, so the server is running and named is > > re

Re: Loopback configuration

p address and port number and others have confirmed they are > > available on the www, so the server is running and named is > > resolving properly outside the LAN. > > > > > > This is the hosts.conf, where I think my error might lie: > > > > > > > >

Re: Loopback configuration

l 192.168 > ip address and port number and others have confirmed they are > available on the www, so the server is running and named is > resolving properly outside the LAN. > > > This is the hosts.conf, where I think my error might lie: > > > > > >

Loopback configuration

, so the server is running and named is resolving properly outside the LAN. This is the hosts.conf, where I think my error might lie: > ## > # Host Database > # > # localhost is used to configure the loopback interface > # when the system is booting. Do not change this entry. &

Re: Loopback alias

Hi Mark, Thank you for your prompt answer and for taking off my worries that I'm missing something there. Best Regards, Julian - Original Message - From: "Mark Andrews" To: "ic.nssip" Cc: Sent: Thursday, March 04, 2010 1:30 PM Subject: Re: Loop

Re: Loopback alias

re configured I: as alias addresses on the loopback interface. Please run I: "bin/tests/system/ifconfig.sh up" as root to configure them I: and rerun the tests. Is this alias request just for test purpose, Yes. The tests mentioned involve setting up a number of

Re: Loopback alias

e IP addresses 10.53.0.1 through 10.53.0.5 are configured > I: as alias addresses on the loopback interface. Please run > I: "bin/tests/system/ifconfig.sh up" as root to configure them > I: and rerun the tests. > > Is this alias request just for test purpose

Loopback alias

ddresses on the loopback interface. Please run I: "bin/tests/system/ifconfig.sh up" as root to configure them I: and rerun the tests. Is this alias request just for test purpose, or it affects the functionality and the performance of DNS Server as well after it goes live? It was