>>> doing the above testing I was running named as root, in order to
>>> generate a core dump. When I'm now testing with named running as
>>> user bind (and then dropping privileges after startup), it seems to
>>> be unable to rebind to port 853 after an "rndc reconfigure". This
>>> is probably exp
> On 31. 1. 2022, at 16:30, sth...@nethelp.no wrote:
>
>> Followup: Unfortunately, this didn't solve the whole problem. While
>> doing the above testing I was running named as root, in order to
>> generate a core dump. When I'm now testing with named running as
>> user bind (and then dropping pri
> Followup: Unfortunately, this didn't solve the whole problem. While
> doing the above testing I was running named as root, in order to
> generate a core dump. When I'm now testing with named running as
> user bind (and then dropping privileges after startup), it seems to
> be unable to rebind to
(Also sending to bind-users as bind-workers is scheduled to be shutdown.)
>>> If I start named, then (without changing named.conf) do "rndc reconfig"
>>> and then send named a DoT query (dig +tls or kdig +tls) named dies with
>>>
>>> Jan 11 13:45:53 dns named[78236]: netmgr/tlsdns.c:1517: fatal e
4 matches
Mail list logo
