[Solved] Bind9 + TCP_FASTOPEN => no rndc

On Thu, Sep 28, 2017 at 03:28:17PM +, Christopher Sean Hilton wrote: > On Thu, Sep 28, 2017 at 02:20:47PM +, Christopher Sean Hilton wrote: > > Great, > > > > I assumed that the FASTOPEN failure was related to the inablity to > > open the rndc socket. I'll have to debug the rndc socket

Re: Bind9 + TCP_FASTOPEN => no rndc

On Thu, Sep 28, 2017 at 02:20:47PM +, Christopher Sean Hilton wrote: > Great, > > I assumed that the FASTOPEN failure was related to the inablity to > open the rndc socket. I'll have to debug the rndc socket seperately. > > > Thanks for help! > This had nothing to do with FASTOPEN and

Re: Bind9 + TCP_FASTOPEN => no rndc

On Wed, Sep 27, 2017 at 09:17:29PM +, Dimitry Andric wrote: > On 27 Sep 2017, at 19:35, Christopher Sean Hilton wrote: > > > > I'm trying to configure bind 9.11 as a nameserver on FreeBSD > > 11-STABLE. When the bind9 port compile it enables TCP_FASTOPEN but the > >

Re: Bind9 + TCP_FASTOPEN => no rndc

On Wed, Sep 27, 2017 at 05:51:31PM +, David Wolfskill wrote: > On Wed, Sep 27, 2017 at 01:35:25PM -0400, Christopher Sean Hilton wrote: > > I'm trying to configure bind 9.11 as a nameserver on FreeBSD > > 11-STABLE. When the bind9 port compile it enables TCP_FASTOPEN but the > > changes

Re: Bind9 + TCP_FASTOPEN => no rndc

On 09/27/17 at 01:35P, Christopher Sean Hilton wrote: > I'm trying to configure bind 9.11 as a nameserver on FreeBSD > 11-STABLE. When the bind9 port compile it enables TCP_FASTOPEN but the > changes haven't yet been baked into the GENERIC Kernel. I can't find a > way to disable the use of

Bind9 + TCP_FASTOPEN => no rndc

I'm trying to configure bind 9.11 as a nameserver on FreeBSD 11-STABLE. When the bind9 port compile it enables TCP_FASTOPEN but the changes haven't yet been baked into the GENERIC Kernel. I can't find a way to disable the use of TCP_FASTOPEN in bind at startup. Is the only way to fix this problem