-query { red-hats; };
allow-recursion { red-hats; };
}
This example contains two access control lists, black-hats and red-hats.
Hosts in the black-hats list are denied access to the nameserver, while
hosts in the red-hats list are given normal access.
Regards
TCPWave Customer
Greg,
You can use a tool called fping to find out what's alive on your
network. http://fping.sourceforge.net/
# fping -g 192.168.1.0/30
192.168.1.1 is alive
192.168.1.2 is unreachable
192.168.1.3 is unreachable
Thanks
Sam.
On Tue, 2011-08-23 at 13:16 +1200, Gregory Machin wrote:
> Hi.
>
>
Dennis
What's the OS are you are using? What's the compiler version used and
what are the compiler options used to build the binary? How are you
measuring the memory utilization? Does the RSS of named grow over time?
thanks
Sam.
On Wed, 2011-08-10 at 00:31 +1000, Dennis Perisa wrote:
> Hi folks,
> On Sat, Jul 9, 2011 at 10:56 PM, TCPWave Customer Care
> wrote:
> Hi BIND Users,
>
> In one of our customer sites, the DNS process was found
> running on
> multiple cache serversbut is was not responding to a dig
> @localhost.
lame-ttl is an option in named.conf which defines the number of seconds
to cache lame delegations or lame servers i.e servers which are marked
as authoitative but do not respond as authoritative. Set that option to
0 so that you will never cache a bad delegation.
max-ncache-ttl sets the maximum t
Can you send the process table from your system?
On Sat, 2011-07-16 at 10:06 -0400, Warren Kumari wrote:
> A related question (and apologies for the top post...)
>
> Does anyone know a good way to figure out the process that is making queries?
> Every 30 minutes or so I get 500 - 600 for aroun
to keep up to date using
RFC 5011 trust anchor maintenance. If you are not using DNSSEC, you
don't need this file.
Thanks
TCPWave Customer Care Team
On Sun, 2011-07-10 at 12:30 +0300, Emil Natan wrote:
> Hi,
>
> I have few boxes running BIND 9.7.3-P3. I do not use DNSSEC (for now)
Hi BIND Users,
In one of our customer sites, the DNS process was found running on
multiple cache serversbut is was not responding to a dig @localhost.
The named version is BIND 9.5.1-P2 with security fixes from BIND
9.5.2-P3.
The named process was in a hung state. The recursive cache could not
c
8 matches
Mail list logo