Re: Bind 9.16 port error still lingers

2020-05-04 Thread Christoph Moench-Tegeder
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > Well I did find a dead zone and still no dice. That's unfortunate. Completely nothing in config, zones, journals (if any)? Then it's either something totally obvious (obvious like an elephant in the room) which we're missing; or

Re: Bind 9.16 port error still lingers

2020-05-03 Thread The Doctor via freebsd-ports
On Sun, May 03, 2020 at 03:32:39PM +0200, Christoph Moench-Tegeder wrote: > ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > > > Then let's look at the file: > > I'd think you better run named-checkconf yourself on your file - that > way you get the full file (and all related

Re: Bind 9.16 port error still lingers

2020-05-03 Thread Christoph Moench-Tegeder
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > Then let's look at the file: I'd think you better run named-checkconf yourself on your file - that way you get the full file (and all related config) checked as it exists on your system - not a partial file with "whatever the mail

Re: Bind 9.16 port error still lingers

2020-05-03 Thread Dewayne Geraghty
I think a few people have given the advise that you should look at the placement of your pid file. I don't know what the default is, but I have pid-file "/var/run/named/pid"; in my named.conf file. This ensures that I'm able to successfully run named as the bind user and the pid

Re: Bind 9.16 port error still lingers

2020-05-02 Thread Eugene Grosbein
03.05.2020 0:29, The Doctor via freebsd-ports wrote: > Then let's look at the file: [skip] Quickest way to unbreak your server: take default named.conf from the installation of version 9.16 and add your changes to it manually but keep default paths within lines "pid-file" and alike. That is,

Re: Bind 9.16 port error still lingers

2020-05-02 Thread Eugene Grosbein
03.05.2020 1:13, Per olof Ljungmark wrote: > On 2020-05-02 19:29, The Doctor via freebsd-ports wrote: >> On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote: >>> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > [snip] > >> //Use with the following in

Re: Bind 9.16 port error still lingers

2020-05-02 Thread Per olof Ljungmark
On 2020-05-02 19:29, The Doctor via freebsd-ports wrote: On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote: ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): [snip] //Use with the following in named.conf, adjusting the allow list as needed: key "rndc-key"

Re: Bind 9.16 port error still lingers

2020-05-02 Thread The Doctor via freebsd-ports
On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote: > ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > > > > > Subject: Bind 9.16 port error still lingers > > > > > > "Still"? > > You seemed to imply that t

Re: Bind 9.16 port error still lingers

2020-05-02 Thread Christoph Moench-Tegeder
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > > > Subject: Bind 9.16 port error still lingers > > > > "Still"? You seemed to imply that there was a known problem in our bind port. While I doubt the existence of a problem with this severity (at l

Re: Bind 9.16 port error still lingers

2020-05-02 Thread Michael Butler via freebsd-ports
On 5/2/20 11:16 AM, The Doctor via freebsd-ports wrote: > On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote: >> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): >> >>> Subject: Bind 9.16 port error still lingers >> >> "

Re: Bind 9.16 port error still lingers

2020-05-02 Thread David Wolfskill
gt;> > >>> Subject: Bind 9.16 port error still lingers > >> > >> "Still"? > >> > >>> May 1 21:29:02 gallifrey named[90441]: Required root permissions to open > >>> '/var/run/named.pid'. > >>> May 1 21:29:02 galli

Re: Bind 9.16 port error still lingers

2020-05-02 Thread Per olof Ljungmark
On 2020-05-02 17:16, The Doctor via freebsd-ports wrote: On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote: ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): Subject: Bind 9.16 port error still lingers "Still"? May 1 21:29:02 gallifrey n

Re: Bind 9.16 port error still lingers

2020-05-02 Thread The Doctor via freebsd-ports
On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote: > ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > > > Subject: Bind 9.16 port error still lingers > > "Still"? > > > May 1 21:29:02 gallifrey named[90441]: Required ro

Re: Bind 9.16 port error still lingers

2020-05-02 Thread Christoph Moench-Tegeder
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org): > Subject: Bind 9.16 port error still lingers "Still"? > May 1 21:29:02 gallifrey named[90441]: Required root permissions to open > '/var/run/named.pid'. > May 1 21:29:02 gallifrey named[90441]: Please ch

Bind 9.16 port error still lingers

2020-05-02 Thread The Doctor via freebsd-ports
May 1 21:29:00 gallifrey named[3026]: invalid command from 127.0.0.1#16349: bad auth May 1 21:29:00 gallifrey named[3026]: stopping command channel on 127.0.0.1#953 May 1 21:29:02 gallifrey named[3026]: exiting May 1 21:29:02 gallifrey named[90441]: starting BIND 9.16.2 (Stable Release)