Don't know if you can control the default query type, but this is a RTFM
(see man dig):
It is possible to set per-user defaults for dig via ${HOME}/.digrc. This
file is read and any options in it are applied before the command line
arguments.
On Wed, Jun 25, 2014 at 10:10 AM, Barry Margolin
This got me to take a look at rndc recursing on one of our servers.
It is disappointing that queries for the same FQDN/type/class from the same
client (different source port and query ID though) are handled individually
rather than being merged somehow. Is this because of the ID or the source
One thing that has always been a mystery to me is what the difference is
between the hard and soft limits on recursion - i.e. the default limit on
recursion is 1000 which means that the soft limit is not in effect. When
the limit is reached, the oldest query is always dropped, but without a
soft
In our case, our on-campus public recursive servers run 2 instances, one
for local applications only and the other for the public. We implemented
it almost exactly as you describe and it works great.
Scott
On Fri, May 18, 2012 at 10:48 AM, Barry Margolin bar...@alum.mit.eduwrote:
In article
4 matches
Mail list logo
