Re: Problems in views in a zone transfer

2011-05-26 Thread Luis Silva
Hi all, I have this configuration in the zone.conf: view VIEW1 { match-clients { 10.112.25.184; // IPs you want to access this view 10.112.25.185; // Note: you must include the IP of // the master to receive notifications. };

Re: Problems in views in a zone transfer

2011-05-26 Thread Luis Silva
Hi all, I think I have found a solution. Don't know if it is the best one: For example, for view1 i added !key view2-resolver; to the match-clients. view VIEW1 { match-clients { !key view2-resolver.; 10.112.25.184; // IPs you want to access this view

Bug in bind 9.7.3?

2011-05-26 Thread Frank Kloeker
Hi, I using bind 9.7.3 as resolver in a slightly larger server farm with some mail servers that use domain key validation. If a try # host -t TXT _adsp._domainkey.federalreserve.gov bind dies with May 26 19:59:02 resolv04 named[8237]: buffer.c:285: REQUIRE(b-used + 1 = b-length) failed May 26

Re: Problems in views in a zone transfer

2011-05-26 Thread Evan Hunt
server 10.112.25.184 {keys view1-resolver.; }; // master Is there a best way? Your way is fine. You can also specify a key in the masters statement, e.g: view internal { match-clients { !key external-key; internal-acl; }; zone example.com { type

recursive server querying authoritative - timeout before trying next server?

2011-05-26 Thread Dan Pritts
Hi, A question regarding BIND defaults. I'd love the same answer for other nameserver software if anyone cares to share. I am a recursive nameserver. I am looking for foo.bar.com. i've learned from bar.com that foo.bar.com has four NS records. I've never tried to talk to these servers

Re: Bug in bind 9.7.3?

2011-05-26 Thread Michael Sinatra
On Thu, 26 May 2011, Frank Kloeker wrote: Hi, I using bind 9.7.3 as resolver in a slightly larger server farm with some mail servers that use domain key validation. If a try # host -t TXT _adsp._domainkey.federalreserve.gov bind dies with May 26 19:59:02 resolv04 named[8237]:

Re: Bug in bind 9.7.3 [ and 9.8.0]

2011-05-26 Thread Jan-Piet Mens
# host -t TXT _adsp._domainkey.federalreserve.gov bind dies with May 26 19:59:02 resolv04 named[8237]: buffer.c:285: REQUIRE(b-used + 1 = b-length) failed May 26 19:59:02 resolv04 named[8237]: exiting (due to assertion failure) This is reproducible and should only affected in 9.7.3.

Re: Bug in bind 9.7.3?

2011-05-26 Thread Andris Kalnozols
I using bind 9.7.3 as resolver in a slightly larger server farm with some mail servers that use domain key validation. If a try # host -t TXT _adsp._domainkey.federalreserve.gov bind dies with May 26 19:59:02 resolv04 named[8237]: buffer.c:285: REQUIRE(b-used + 1 = b-length) failed

Re: Bug in bind 9.7.3?

2011-05-26 Thread Evan Hunt
I using bind 9.7.3 as resolver in a slightly larger server farm with some mail servers that use domain key validation. We're investigating the problem. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. ___ bind-users mailing list

Re: Bug in bind 9.7.3?

2011-05-26 Thread SM
Hi Frank, At 11:33 26-05-2011, Frank Kloeker wrote: I using bind 9.7.3 as resolver in a slightly larger server farm with some mail servers that use domain key validation. If a try # host -t TXT _adsp._domainkey.federalreserve.gov This occurs with BIND 9.8.0: buffer.c:285: REQUIRE(b-used + 1

Re: Bug in bind 9.7.3?

2011-05-26 Thread David Sparro
On 5/26/2011 2:33 PM, Frank Kloeker wrote: Hi, I using bind 9.7.3 as resolver in a slightly larger server farm with some mail servers that use domain key validation. If a try # host -t TXT _adsp._domainkey.federalreserve.gov bind dies with May 26 19:59:02 resolv04 named[8237]: buffer.c:285:

Re: recursive server querying authoritative - timeout before trying next server?

2011-05-26 Thread lst_hoe02
Zitat von Dan Pritts da...@internet2.edu: Hi, A question regarding BIND defaults. I'd love the same answer for other nameserver software if anyone cares to share. http://www.unbound.net/documentation/info_timeout.html For sure Bind is doing something similar. Regards Andreas

Re: Bug in bind 9.7.3?

2011-05-26 Thread Hauke Lampe
I can't get my 9.8.0-P1 resolvers to crash. The response from the federalreserve.gov servers looks strange, though: dig +dnssec +ignore +norec federalreserve.gov soa @ns5.frb.gov ;; Warning: Message parser reports malformed message packet. ;; WARNING: Messages has 57 extra bytes at end Hauke.

Re: Bug in bind 9.7.3?

2011-05-26 Thread Eivind Olsen
David Sparro wrote: I had some of my 9.7.2-P3 boxes die the same way as well. dig txt _policy._domainkey.federalreserve.gov will trigger the crash as well. Not all of my systems seem to be affected, though. Those that are seem to be 100% reproducible. Just out of curiosity - are anyone

Re: recursive server querying authoritative - timeout before trying next server?

2011-05-26 Thread Kevin Darcy
On 5/26/2011 2:51 PM, Dan Pritts wrote: Hi, A question regarding BIND defaults. I'd love the same answer for other nameserver software if anyone cares to share. I am a recursive nameserver. I am looking for foo.bar.com. i've learned from bar.com that foo.bar.com has four NS records. I've

Re: Bug in bind 9.7.3?

2011-05-26 Thread Evan Hunt
Just out of curiosity - are anyone seeing these crashes with a BIND that isn't doing DNSSEC validation? Yes. But the problem domain has been corrected, so you won't be able to reproduce it now. In the interest of preventing this happening again, either by accident (as it was in this case) or

Re: Bug in bind 9.7.3?

2011-05-26 Thread Eivind Olsen
I wrote: (I've not been able to reproduce this on any non-validating server yet, and my validating servers are running some other software at the moment - I'll enable validation on my test systems and check if I can get them to crash). I've so far not been able to reproduce it on a