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.
}
__
Introduction
BIND 9.8.1b1 is the first beta release of BIND 9.8.1, a maintenance
release for BIND 9.8.
Please see the CHANGES file in the source code release for a complete
list of all changes. See below for a l
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
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
> 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 sl
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 befor
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]: buffer.c:285:
> # 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 i
> 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->lengt
> 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
bind-
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
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: R
Zitat von Dan Pritts :
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
___
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.
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
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
> 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
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 DNSSEC
> Date: Fri, 27 May 2011 01:32:05 +0200
> From: "Eivind Olsen"
> Sender: bind-users-bounces+oberman=es@lists.isc.org
>
> 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'
19 matches
Mail list logo
