What is BIND internal logic when such a series of queries are received, and
why it would not answer to all requests.
Regards,
Samer Khattab
On Sun, Feb 5, 2012 at 9:42 AM, Mark Andrews wrote:
>
> In message oky1lepdf...@mail.gmail.com>
> , Samer Khattab writes:
> > Hi all,
client IP,source port and Server IP is the same in these queries.
Is this the right BIND behavior in this case or it is an issue.
Regards,
Samer Khattab
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
This is from an ISC compiled source.
On Wed, Nov 16, 2011 at 2:39 PM, Florian Weimer wrote:
> * Samer Khattab:
>
> > I found the following in the logs:
> >
> > 16-Nov-2011 08:26:58.724 query.c:1781: INSIST(!
> > dns_rdataset_isassociated(sigrdataset)) failed,
0x3ab60d3d1d in _fini()+0x3ab5b51125
16-Nov-2011 08:26:58.738 exiting (due to assertion failure)
On Wed, Nov 16, 2011 at 1:01 PM, Stephane Bortzmeyer wrote:
> On Wed, Nov 16, 2011 at 12:08:59PM +0400,
> Samer Khattab wrote
> a message of 38 lines which said:
>
> > 8 of our cashing
8 of our cashing-only name servers crashed in a random sequence, and the
crash happened in a 10 minutes time. The servers are running BIND 9.7.3-P3.
The crash produced a core dump for the named process.
Does anybody has a similar case recently? Is this a security issue ?
Regards,
Samer
gure --your-options
>
> then recompile
>
>
> On 09/27/2010 01:27 PM, Samer Khattab wrote:
>
>> Hi all,
>>
>> I'm using Bind as a caching name server and serving around 2000 req per
>> second, and recently have the following messages showing up from tim
Hi all,
I'm using Bind as a caching name server and serving around 2000 req per
second, and recently have the following messages showing up from time to
time in the general.log.
27-Sep-2010 10:45:47.639 sockmgr 0x2ad7af2f5010: maximum number of FD events
(64) received
27-Sep-2010 10:45:47.872 so
Bind suffered from a crash on one of our caching servers, a core dumb for
named was generated.
We are running BIND 9.7.1-P2, on rhel 5.5, kernel 2.6.18-194.el5.
The only useful log lines found at the crash time are from "general.log",
following are the lines:
27-Aug-2010 16:43:04.901 query.c:178
8 matches
Mail list logo
