Date: Sun, 3 May 2020 15:32:39 +0200 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: freebsd-ports@freebsd.org Subject: Re: Bind 9.16 port error still lingers Message-ID: <20200503133239.GA14877@elch.exwg.net> In-Reply-To: <20200502172907.GA59662@doctor.nl2k.ab.ca> References: <20200502140501.GA16385@doctor.nl2k.ab.ca> <20200502143210.GA4453@elch.exwg.net> <20200502151636.GA22397@doctor.nl2k.ab.ca> <20200502165318.GB4453@elch.exwg.net> <20200502172907.GA59662@doctor.nl2k.ab.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
## 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 systems in between did". Just a few remark: - you included a control key - even if it's restricted to localhost, it's good practice to generate a new one - when you're at that, you could also switch to a newer algorithm for that control channel - hmac-sha256 or whatever - there's an unused acl - your indentation is all over the place, which makes for a more difficult reading than neccessary - network masks are used in a somewhat inconstant manner, that may result in funny debugging later on (that's me talking from experience) Regards, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200503133239.GA14877>