Re: NSD logging control connection when using a filesystem socket

Wouter Wijngaards <[email protected]> Mon, 13 Aug 2018 15:25:07 +0200

Newsgroups	gmane.network.dns.nsd.general
Message-ID	<[email protected]>

Hi Anand,

On 08/13/2018 03:03 PM, Anand Buddhdev wrote:
> Hi NSD developers,
> 
> I'm using the new filesystem socket feature of NSD 4.1.24 to control it,
> and I've noticed this in the log:

Yes that is not right, it printed the addr variable but it has no
contents when a unix socket is used.  Instead I have fixed it to print
the local socket path name (if it is a local socket).  The fix is in the
code repository.  Thanks for the report!

Best regards, Wouter

> 
> [2018-08-13 12:55:37.861] nsd[26856]: info: new control connection from
> 0.0.0.0
> [2018-08-13 12:55:37.862] nsd[26856]: info: control cmd:  transfer
> [2018-08-13 12:56:39.501] nsd[26856]: info: new control connection from
> 0.0.1.0
> [2018-08-13 12:56:39.501] nsd[26856]: info: control cmd:  status
> [2018-08-13 13:00:15.481] nsd[26856]: info: new control connection from
> 0.0.1.0
> [2018-08-13 13:00:15.481] nsd[26856]: info: control cmd:  transfer
> [2018-08-13 13:00:19.921] nsd[26856]: info: new control connection from
> 19.0.0.0
> [2018-08-13 13:00:19.921] nsd[26856]: info: control cmd:  status
> 
> Notice the "new control connection from ..." lines. They look like IP
> addresses, and they're not consistent (0.0.0.0, 0.0.1.0, 19.0.0.0). Is
> this a bug?
> 
> Anand
> _______________________________________________
> nsd-users mailing list
> [email protected]
> https://open.nlnetlabs.nl/mailman/listinfo/nsd-users
>

_______________________________________________
nsd-users mailing list
[email protected]
https://open.nlnetlabs.nl/mailman/listinfo/nsd-users

signature.asc (application/pgp-signature, 833 B)