[nsd-users] ip-address <-> control-interface

[Willem Toorop]

Hi Andreas,

I don't think that difference was intentional.
I've created a PR to resolve it:

	https://github.com/NLnetLabs/nsd/pull/156

Thanks for pointing it out!

Cheers,
-- Willem

Op 13-02-2021 om 20:18 schreef A. Schulze via nsd-users:
> Hello NSD-Developers,
> 
> the "ip-address" statement accept an interface name. NSD will listen on ip-addresses associated with that interface.
> That's nice.
> 
> But the same does not work for "control-interface". Is this intentional?
> 
> server:
>  ip-address: eth0
>  verbosity: 9
> remote-control:
>  control-enable: yes
>  control-interface: eth1
> 
> [2021-02-13 20:11:25.801] nsd[104]: info: interface eth0 has address 192.0.2.53
> [2021-02-13 20:11:25.801] nsd[104]: notice: nsd starting (NSD 4.3.5)
> [2021-02-13 20:11:25.801] nsd[104]: notice: listen on ip-address 192.0.2.53 at 53 (udp) with server(s): *
> [2021-02-13 20:11:25.801] nsd[104]: notice: listen on ip-address 192.0.2.53 at 53 (tcp) with server(s): *
> [2021-02-13 20:11:25.804] nsd[104]: error: control interface eth1:8952 getaddrinfo: Name or service not known 
> [2021-02-13 20:11:25.804] nsd[104]: error: could not open remote control port
> [2021-02-13 20:11:25.804] nsd[104]: error: could not perform remote control setup
> 
> Andreas
> _______________________________________________
> nsd-users mailing list
> nsd-users at lists.nlnetlabs.nl
> https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
>