On 24/07/2014 01:35, Matthew Calder wrote:
> At the moment I'm limited to using 2 UDP listeners per interface. When
> stress testing I can see that only 2 out of 4 CPUs are being used, I'm
> guessing because I'm limited to 2 listeners. Any suggestions for what
> could be limiting BIND from using a
==
>> > > Content-Type: multipart/alternative;
>> > boundary=089e013a044a72db8004fe551784
>> > >
>> > > --089e013a044a72db8004fe551784
>> > > Content-Type: text/plain; charset=UTF-8
>> > >
>&g
n BIND
> > > 9.9.5-3-Ubuntu (Extended Support Version) on Ubuntu 14.04 and
> > seeing this
> > > error on startup/reload.
> > >
> > > Jul 15 19:20:57 named[1978]: server.c:2772: unexpected error:
> > > Jul 15 19:20:
configuration. I'm running on BIND
> > 9.9.5-3-Ubuntu (Extended Support Version) on Ubuntu 14.04 and
> seeing this
> > error on startup/reload.
> >
> > Jul 15 19:20:57 named[1978]: server.c:2772: unexpected error:
> > Jul 15 19:20:57 nam
) on Ubuntu 14.04 and seeing this
> > error on startup/reload.
> >
> > Jul 15 19:20:57 named[1978]: server.c:2772: unexpected error:
> > Jul 15 19:20:57 named[1978]: unable to obtain neither an IPv4 nor an IPv6
> > dispatch
> >
> > This happens if I do rndc
erver.c:2772: unexpected error:
> Jul 15 19:20:57 named[1978]: unable to obtain neither an IPv4 nor an IPv6
> dispatch
>
> This happens if I do rndc reload/reconfig. My named.conf.local has
> many around 500 views and large match-client ACLs because I am
> experimenting with a glob
I'm completely new to BIND configuration. I'm running on BIND
9.9.5-3-Ubuntu (Extended Support Version) on Ubuntu 14.04 and seeing this
error on startup/reload.
Jul 15 19:20:57 named[1978]: server.c:2772: unexpected error:
Jul 15 19:20:57 named[1978]: unable to obtain neither an IPv4 n
7 matches
Mail list logo
