Am 17.02.21 um 19:50 schrieb Willem Toorop via nsd-users:> I don't think that difference was intentional. > I've created a PR to resolve it: > > https://github.com/NLnetLabs/nsd/pull/156Hi Willem, that's cool. It enable docker-user to setup nsd to listen for control connection over a docker bridge with a non-deterministic ip network. Can't say, it works because I've to modify my build-system (today I build nsd only from released tar.gz ...) Andreas
Am 18.02.21 um 00:06 schrieb A. Schulze via nsd-users:> Can't say, it works because I've to modify my build-system (today I build nsd only from released tar.gz ...)now: root at 233ad0e3d5b6:/usr/local/etc/nsd# cat nsd.conf server: ip-address: 127.0.0.1 at 1025 verbosity: 9 remote-control: control-enable: yes control-interface: eth0 root at 233ad0e3d5b6:/usr/local/etc/nsd# nsd [2021-02-18 17:25:35.292] nsd[75]: info: interface eth0 has address 172.18.0.2 [2021-02-18 17:25:35.293] nsd[75]: notice: nsd starting (NSD 4.3.6) [2021-02-18 17:25:35.293] nsd[75]: notice: listen on ip-address 127.0.0.1 at 1025 (udp) with server(s): * [2021-02-18 17:25:35.293] nsd[75]: notice: listen on ip-address 127.0.0.1 at 1025 (tcp) with server(s): * root at 233ad0e3d5b6:/usr/local/etc/nsd# netstat -lnpt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:1025 0.0.0.0:* LISTEN - tcp 0 0 172.18.0.2:8952 0.0.0.0:* LISTEN - But: root at 233ad0e3d5b6:/usr/local/etc/nsd# nsd-control status could not parse IP: eth0> > Andreas