Is there a way to count the number of queries?

Hi everyone, Would please someone tell me a way to count the queries that my DNS server received? I also want to count the number of queries from a specific IP address. Can anyone tell me how to do that? Thanks ___ Please visit

?????? Re: Is there a way to count the number of queries?

So can I set the statistic option in specific View option? If I can do that, it can record the number of queries by specific IP. -Original Message- From: Feng He fen...@nsbeta.info Sender: bind-users-bounces+xuezxbb=gmail@lists.isc.orgDate: Wed, 07 Nov 2012 17:51:57 To:

Re: Is there a way to count the number of queries?

On Nov 7, 2012, at 3:51 AM, Feng He fen...@nsbeta.info wrote: 于 2012-11-7 17:39, Tony Xue 写道: Would please someone tell me a way to count the queries that my DNS server received? I also want to count the number of queries from a specific IP address. BIND has a zone-statistics option

Shared dynamic zone on external view?

Hello, I have a dynamic zone on an external view, this zone is updated with a TSIG key from outside of our network. There is a secondary DNS server, also outside our network on which zones transfers are working fine with no key. We would like to make one of our internal DNS secondary for

Should Root Servers Always be Queried First? bind9.7.7

If I do: dig @localhost +short +trace somehost.okstate.edu on a server authoritative for the okstate.edu domain, I would expect resolution via that authoritative system. I do get it but the query takes the scenic route and I get all the root name servers just as if the query was for some host

Re: Should Root Servers Always be Queried First? bind9.7.7

-Original Message- From: Martin McCormick mar...@dc.cis.okstate.edu Date: Wednesday, November 7, 2012 1:12 PM To: bind-users@lists.isc.org bind-users@lists.isc.org Subject: Should Root Servers Always be Queried First? bind9.7.7 If I do: dig @localhost +short +trace somehost.okstate.edu

RE: Should Root Servers Always be Queried First? bind9.7.7

The +trace option ignores the resolver that you specify after the @ sign, and begins at the root. -DTK -Original Message- From: bind-users-bounces+root=nachtmaus...@lists.isc.org [mailto:bind-users-bounces+root=nachtmaus...@lists.isc.org] On Behalf Of Martin McCormick Sent:

Re: Should Root Servers Always be Queried First? bind9.7.7

In other words, if your goal is to identify latency in your resolver, it's probably best to run tcpdump on the resolver itself, and analyze the traffic capture to see if there are any latency. The +trace shows you what should happen. On Wed, Nov 7, 2012 at 3:05 PM, david r...@nachtmaus.us wrote:

Re: Should Root Servers Always be Queried First? bind9.7.7

Thanks to all who reminded me how dig resolves lookups. I have since learned that we are apparently having intermittent network issues that are causing a lot of systems to behave oddly and our DNS's are only reflecting those conditions. We were taking anywhere from 0 milliseconds

Re: Shared dynamic zone on external view?

In message 509a8796.7060...@nryc.fr, Nicolas C. writes: Hello, I have a dynamic zone on an external view, this zone is updated with a TSIG key from outside of our network. There is a secondary DNS server, also outside our network on which zones transfers are working fine with no key.