Re: bind 9.16 vs. 9.14 tcp client connections

On 13.04.20 21:07, sth...@nethelp.no wrote: >> general: error: TCP connection failed: quota reached > > I had some of these too, until I explicitly set this named option: > > tcp-listen-queue 20; > > Looks like the default is 10. The way I interpret this parameter is > that this sets the *oper

Re: Try to figure a basic conf for BIND on Mac Catalina

I have been working on this for days. Anything other than Caching-only configuration will not register anything. Port 53 will not open. Looking for help with a configuration that will allow this server to be authority for 2 domains focushm.com and focushs.com and forward for all others. Don’t k

Re: BIND-9.16.1 & KASP

Thanks for the reply On 2020/04/14 08:42, Matthijs Mekking wrote: Mark, On 4/13/20 8:54 PM, Evan Hunt wrote: On Mon, Apr 13, 2020 at 02:22:53PM +0200, Mark Elkins wrote: Question - What are the "TYPE65534" records? What are they saying? I am using "DiG 9.16.1" so surprised it doesn't know

Debian/Ubuntu: Why was the service renamed from bind9 to named?

Hello! What is the rationale of: bind9 (1:9.13.6-1) experimental; urgency=medium ... * Rename the init scripts to named to match the name of the daemon Since years, Debian and Ubuntu User, and plenty of scripts and automation software (Puppet ...), know that the service is called "bind9". I

Re: Debian/Ubuntu: Why was the service renamed from bind9 to named?

Am 15.04.20 um 08:51 schrieb Klaus Darilion: > Hello! > > What is the rationale of: > > bind9 (1:9.13.6-1) experimental; urgency=medium > ... > * Rename the init scripts to named to match the name of the daemon > > > Since years, Debian and Ubuntu User, and plenty of scripts and automation