On 21.12.08 04:21, Jack Tavares wrote:
as specified, wouldn't this zone then be non-authoritative
I believe BIND doesn't check NS Records when deciding if it should set the
AA flag and only takes care about the records being from zone
(master/slave) or authoritative source (for AA records) or
Thanks to everybody so far. I am still confused trying to figure this out.
At the risk of looking stupid...
Given this zone file.
$TTL 500
$ORIGIN 168.192.in-addr.arpa.
@ IN SOA d62.test.net. hostmaster.d62.test.net.. 2008122201
10800 3600 604800 86400
NS
At Mon, 22 Dec 2008 01:47:37 -0800 (PST),
y...@irc.pl wrote:
I think to change to version 9.4.3 because of interesing feature
acache.
I would like to speed up response time for my clients.
My DNS server is mostly (95%) caching-only:
NLWP USERNAME SWAP RSS MEMORY TIME CPU
7 named
At Mon, 22 Dec 2008 16:13:10 -0800,
Doug Barton do...@freebsd.org wrote:
And can someone please state affirmatively that the patches to acl.c
and iptable.c do the right thing, with or without the patch to the port?
This patch completely fixed the hole in my test environment. With
this patch
I have confirmed that the ARCH=x86_64 trick resolved the issues with my
configuration. I have tested this with an authoritative and recursive
dns/bind95 port with modified Makefile.
I have not fully tested the acl.c and iptable.c since the patch suit my need.
Thanks!
--- On Tue, 12/23/08,
5 matches
Mail list logo