Hi Mike,
When BIND first introduced this Case-Insensitive Response Compression
(See https://kb.isc.org/article/AA-01113) I found out that BIND
zone_name case sensitivity in a zone statement is preferred over name
case sensitivity in the zone itself.
So, you can get a google.COM answer because the
On Thu, Mar 31, 2016 at 2:00 PM, Michael Brunnbauer wrote:
>
> hi all,
>
> On Thu, Mar 31, 2016 at 07:32:21PM +0200, Michael Brunnbauer wrote:
>> Is is possible that is this connected to rndc stats? I will stop doing
>> rndc stats for a while to test (it currently runs every minute).
>
> Not doing
hi all,
On Thu, Mar 31, 2016 at 07:32:21PM +0200, Michael Brunnbauer wrote:
> Is is possible that is this connected to rndc stats? I will stop doing
> rndc stats for a while to test (it currently runs every minute).
Not doing rndc stats did not prevent the problem. Any other ideas?
Regards,
Mi
Hello Steinar,
On Thu, Mar 31, 2016 at 07:35:39PM +0200, sth...@nethelp.no wrote:
> Have you checked your operating system limits? One recursive client
> often means one open socket (waiting for response from authoritative
> server), i.e. one open file descriptor. If you have thousands of
> simul
Tony Finch wrote:
> Phil Mayers wrote:
> >
> > What is considered the source of the ownername for, say, "com."?
>
> It should be the root zone master file.
Why not the com zone master file?
--
Robert Edmonds
___
Please visit https://lists.isc.org/mai
> > If you are crawling lots of new names, the cache size won't have much
> > impact. Each new query will require recursing vs hitting the cache. Try
> > "rndc recursing" and look at what you have sitting around waiting for
> > answers. Hopefully that provides some clues. This can be all sorts
Hello Tony,
On Thu, Mar 31, 2016 at 05:08:43PM +0100, Tony Finch wrote:
> Michael Brunnbauer wrote:
> >
> > I am using bind on a server that does massive crawling with a multithreaded
> > Java app. This server occasionally has to do lookups for hosts in our local
> > zone netestate.de - for whic
Hello Mike,
On Thu, Mar 31, 2016 at 04:05:39PM +, Mike Hoskins (michoski) wrote:
> If you are crawling lots of new names, the cache size won't have much
> impact. Each new query will require recursing vs hitting the cache. Try
> "rndc recursing" and look at what you have sitting around wait
Michael Brunnbauer wrote:
>
> I am using bind on a server that does massive crawling with a multithreaded
> Java app. This server occasionally has to do lookups for hosts in our local
> zone netestate.de - for which it is not authoritative - and those lookups tend
> to fail when the load is high (
If you are crawling lots of new names, the cache size won't have much
impact. Each new query will require recursing vs hitting the cache. Try
"rndc recursing" and look at what you have sitting around waiting for
answers. Hopefully that provides some clues. This can be all sorts of
things like u
hi all,
I am using bind on a server that does massive crawling with a multithreaded
Java app. This server occasionally has to do lookups for hosts in our local
zone netestate.de - for which it is not authoritative - and those lookups tend
to fail when the load is high (e.g. >1000 recursing clien
11 matches
Mail list logo
