On 23/09/2024 13:50, Matthew Seaman wrote:
On 22/09/2024 16:34, Willem Jan Withagen wrote:
On 19/09/2024 20:04, Dan Mack wrote:
On Thu, 19 Sep 2024, Matthew Seaman wrote:
On 19/09/2024 18:16, Dan Mack wrote:
On Tue, 2 Jul 2024, sth...@nethelp.no wrote:
So we set uid 53 (bind) at 0.08
On 22/09/2024 16:34, Willem Jan Withagen wrote:
On 19/09/2024 20:04, Dan Mack wrote:
On Thu, 19 Sep 2024, Matthew Seaman wrote:
On 19/09/2024 18:16, Dan Mack wrote:
On Tue, 2 Jul 2024, sth...@nethelp.no wrote:
So we set uid 53 (bind) at 0.083518302, and then try to bind to
port
953 at
On 19/09/2024 20:04, Dan Mack wrote:
On Thu, 19 Sep 2024, Matthew Seaman wrote:
On 19/09/2024 18:16, Dan Mack wrote:
On Tue, 2 Jul 2024, sth...@nethelp.no wrote:
So we set uid 53 (bind) at 0.083518302, and then try to bind to
port
953 at 0.093282161.
Are you going to poe a bug with
On Thu, 19 Sep 2024, Matthew Seaman wrote:
On 19/09/2024 18:16, Dan Mack wrote:
On Tue, 2 Jul 2024, sth...@nethelp.no wrote:
So we set uid 53 (bind) at 0.083518302, and then try to bind to port
953 at 0.093282161.
Are you going to poe a bug with the bind people?
Already did: https://
On 19/09/2024 18:16, Dan Mack wrote:
On Tue, 2 Jul 2024, sth...@nethelp.no wrote:
So we set uid 53 (bind) at 0.083518302, and then try to bind to port
953 at 0.093282161.
Are you going to poe a bug with the bind people?
Already did: https://gitlab.isc.org/isc-projects/bind9/-/issues/4793
S
On Tue, 2 Jul 2024, sth...@nethelp.no wrote:
So we set uid 53 (bind) at 0.083518302, and then try to bind to port
953 at 0.093282161.
Are you going to poe a bug with the bind people?
Already did: https://gitlab.isc.org/isc-projects/bind9/-/issues/4793
Steinar Haug, AS2116
Probably everyon
>> So we set uid 53 (bind) at 0.083518302, and then try to bind to port
>> 953 at 0.093282161.
>
> Are you going to poe a bug with the bind people?
Already did: https://gitlab.isc.org/isc-projects/bind9/-/issues/4793
Steinar Haug, AS2116
On Mon, 1 Jul 2024, Craig Leres wrote:
On 7/1/24 10:17, Bakul Shah wrote:
On Jul 1, 2024, at 9:18 AM, Craig Leres wrote:
On 6/30/24 04:46, sth...@nethelp.no wrote:
Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
listen to localhost port 953, with the result that rndc doesn
On Tue, 2 Jul 2024, sth...@nethelp.no wrote:
Other info:
- BIND 9.18.24 on the same host works perfectly, with no rndc issues.
- BIND 9.19.24 on the same host also works *if I change it to run as
root* (by default it runs as user bind). The syslog messages are gone,
and rndc works as expected.
>> Other info:
>>
>> - BIND 9.18.24 on the same host works perfectly, with no rndc issues.
>> - BIND 9.19.24 on the same host also works *if I change it to run as
>> root* (by default it runs as user bind). The syslog messages are gone,
>> and rndc works as expected.
>
> That sounds like they try
On 7/1/24 10:17, Bakul Shah wrote:
On Jul 1, 2024, at 9:18 AM, Craig Leres wrote:
On 6/30/24 04:46, sth...@nethelp.no wrote:
Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
listen to localhost port 953, with the result that rndc doesn't work.
Problem is 100% reproducible.
Hi!
> On 6/30/24 04:46, sth...@nethelp.no wrote:
> > Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
> > listen to localhost port 953, with the result that rndc doesn't work.
> > Problem is 100% reproducible.
>
> bind-tools-9.18.27_1 with 14.1-RELEASE-p1 suffers from this as wel
On Jul 1, 2024, at 9:18 AM, Craig Leres wrote:
>
> On 6/30/24 04:46, sth...@nethelp.no wrote:
>> Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
>> listen to localhost port 953, with the result that rndc doesn't work.
>> Problem is 100% reproducible.
>
> bind-tools-9.18.27_1 wi
On 6/30/24 04:46, sth...@nethelp.no wrote:
Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
listen to localhost port 953, with the result that rndc doesn't work.
Problem is 100% reproducible.
bind-tools-9.18.27_1 with 14.1-RELEASE-p1 suffers from this as well.
> If you (as root) temporary chnage
> sysctl net.inet.ip.portrange.reservedhigh=952
> does it work then (as user bind)?
Yes!
Steinar Haug, AS2116
On Sun, 30 Jun 2024, sth...@nethelp.no wrote:
Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
listen to localhost port 953, with the result that rndc doesn't work.
Problem is 100% reproducible.
Environment:
- FreeBSD 13.3-STABLE #n257580
- BIND 9.19.24 installed using "pkg in
>> # rndc status
>> rndc: connect failed: 127.0.0.1#953: connection refused
>>
>> In syslog I can see among the startup messages:
>>
>> Jun 30 12:53:31 nlab0 named[31772]: couldn't add command channel
>> 127.0.0.1#953: permission denied
>> Jun 30 12:53:31 nlab0 named[31772]: couldn't add command
Short description: Fresh install of bind9-devel-9.19.24_1 doesn't
listen to localhost port 953, with the result that rndc doesn't work.
Problem is 100% reproducible.
Environment:
- FreeBSD 13.3-STABLE #n257580
- BIND 9.19.24 installed using "pkg install bind9-devel-9.19.24_1"
- Default (directly
18 matches
Mail list logo
