Re: trace ok but cannot get answer

> Offhand, nothing stands out for me in that config, but I'm not really a > PIX expert. I've heard, however, that the Cisco "fixups" sometimes > create problems. Can anyone comment on whether " > > fixup protocol dns maximum-length 1024" is likely to exhibit the behavior des > cribed earlier?

Re: too many timeouts - disabling EDNS

The log should get less noisy in the next release. 2409. [bug] Only log that we disabled EDNS processing if we were subsequently successful. [RT #18029] Currently the log indicated when we have disabled EDNS processing due to timeouts. Mis-handling of EDNS q

Re: Queries for tjhinc.com

>I wrote, in part: >> Another question arises - if the default max-cache-size is 32M >> (and titania has 2G of memory), and the cache is supposedly full, >> then why is the named_dumpdb file I created yesterday only 818340 >> bytes long? and Mark Andrews replied: > named_dumpdb will usually

Re: Recursive queries fail if query source port is not fixed

I doubt that this is at all pertinent, but I was experiencing similar behavior once I patched a client a few weeks ago and took them off port 53. Recursive requests were failing three out of every four times they were made, yet digs with trace worked. The company uses a crappy Netgear firew

Re: Problem with named of a network error or problem with the configuration on the interconnecting peers?

Andrey G. Sergeev (AKA Andris) wrote: > Greetings Kevin, > > > Thu, 14 Aug 2008 16:47:02 -0400 Kevin Darcy wrote: > > [...] > > >>> I also recommend you to restrict the AXFR queries. >>> >>> >>> >> Why? It's public information, and as you yourself have just >> demonstrated, leaving zo

Re: trace ok but cannot get answer

Offhand, nothing stands out for me in that config, but I'm not really a PIX expert. I've heard, however, that the Cisco "fixups" sometimes create problems. Can anyone comment on whether " fixup protocol dns maximum-length 1024" is likely to exhibit the behavior described earlier? http://www.exp

Re: too many timeouts - disabling EDNS

Hello Latif, Fri, 15 Aug 2008 15:55:38 -0400 Binmakhashen, Latif wrote: > After upgrading to bind-9.5.0-P2, I get many of the following message > in the log. Is this something I need to worry about or can I just > suppress it? Are there any SOHO routers between the box on which BIND is running

too many timeouts - disabling EDNS

After upgrading to bind-9.5.0-P2, I get many of the following message in the log. Is this something I need to worry about or can I just suppress it? I don't' get a response from the command line for the domains associated with the error and I don't seem get anything about most of them from using

Re: 9.5.0-P1: out of memory error - SERVFAIL

On Aug 12, 2008, at 2:12 PM, JINMEI Tatuya / 神明達哉 wrote: > At Tue, 12 Aug 2008 11:36:26 -0700, > Kai Lanz <[EMAIL PROTECTED]> wrote: >> >> Aug 11 04:01:14 pangea named[10832]: resolver.c:3239: unexpected >> error: >> Aug 11 04:01:14 pangea named[10832]: isc_timer_create: out of memory > > Som

Re: Recursive queries fail if query source port is not fixed

At Fri, 15 Aug 2008 10:27:13 +1000, Mark Andrews <[EMAIL PROTECTED]> wrote: > > > > fctx 0x87b7b20(images.yandex.ru/A'): query > > > > fctx 0x87b7b20(images.yandex.ru/A'): done > > > > > > This seems to indicate creating a query socket somehow failed. Can > > > you build BIND by hand to see if yo

Re: selecttest tool

At Thu, 14 Aug 2008 10:46:18 -0500, Walter Gould <[EMAIL PROTECTED]> wrote: > I have found my problem. Your above statement "it seems to be handling a > high volume of queries (several thousands concurrent clients)" was right > on target. I decided to look more closely at the traffic that was >

DNS - multiple question with a single query

I'm currently developing a DNS utility which is working greatly with a single qname in a query. However, if I try to perform a query for multiple qnames I got a format error. I've checked the datagram with Wireshark and the packet is well formed, and by reading the RFCs I can't find anything releva

Re: trace ok but cannot get answer

As Kevin has said, this is likely in the firewall config. Try adding (actually removing): no fixup protocol dns and then probably also: access-list 120 permit tcp any host 211.148.192.133 eq domain access-list 120 permit tcp any host 211.148.192.134 eq domain access-list 120 permit tcp any host

Re: 9.5.0-P2 and socket: too many open file descriptors

At Thu, 14 Aug 2008 11:05:26 -0700, "David Sparks" <[EMAIL PROTECTED]> wrote: > You could add a cmdline option to configure to override the "calculated" > value. ie: > > ./configure --max-fd=256 We've already provided this knob in a different form: ISC_SOCKET_FDSETSIZE. The difficult part is t

Re: trace ok but cannot get answer

Just for the record. This is the same behavior that I have reported in the thread "Recursive queries fail if query source port is not fixed": http://marc.info/?t=12186132932 (It's a long thread, but after a while I discover that using trace works - see http://marc.info/?l=bind-users&m=121