In article mailman.750.1268169970.21153.bind-us...@lists.isc.org,
jcarrol...@cfl.rr.com wrote:
dig was added to Solaris 9. It is not native to Solaris 8 or older.
That would explain why it's only where Chris found it on some of our
range of Solarises (vintage or only slightly worn).
In article mailman.751.1268170620.21153.bind-us...@lists.isc.org,
Mark Andrews ma...@isc.org wrote:
In message 20100309154017.4801c...@the-damian.de, Torsten writes:
Am Wed, 10 Mar 2010 00:44:46 +1100
schrieb Mark Andrews ma...@isc.org:
In message
On Mar 10 2010, Sam Wilson wrote:
In article mailman.750.1268169970.21153.bind-us...@lists.isc.org,
jcarrol...@cfl.rr.com wrote:
dig was added to Solaris 9. It is not native to Solaris 8 or older.
That would explain why it's only where Chris found it on some of our
range of Solarises
Hello,
in Bind 9.6.2 the zone statistics looked like that:
zone
name4.3.2.1.e164.arpa/IN/name
rdataclassIN/rdataclass
serial3/serial
counters
Requestv40/Requestv4
Requestv60/Requestv6
If there is no option recursion yes (or no); specified in named.conf, is the
server still recursive?
Is recursion activated by default if option recursion (yes|no) is missing in
named.conf?
Thank you,
Julian
___
bind-users mailing list
On 3/10/2010 11:37 AM, ic.nssip wrote:
If there is no option recursion yes (or no); specified in
named.conf, is the server still recursive?
Is recursion activated by default if option recursion (yes|no) is
missing in named.conf?
Yes, recursion is activated by default, but who is or is not
ic.nssip wrote:
If there is no option recursion yes (or no); specified in named.conf,
is the server still recursive?
Is recursion activated by default if option recursion (yes|no) is
missing in named.conf?
In modern BIND, allow-recursion defaults to:
{ localhost; localnets; };
Modern being?
-Original Message-
From: bind-users-bounces+jlightner=water@lists.isc.org
[mailto:bind-users-bounces+jlightner=water@lists.isc.org] On Behalf
Of Alan Clegg
Sent: Wednesday, March 10, 2010 2:25 PM
To: bind-users@lists.isc.org
Subject: Re: recursion
ic.nssip wrote:
Lightner, Jeff wrote:
Modern being?
According to CHANGES file:
--- 9.5.0a6 released ---
2206. [security] allow-query-cache and allow-recursion now
cross inherit from each other.
If allow-query-cache is not set in named.conf then
Lightner, Jeff wrote:
Modern being?
Actually
In the 9.4 CHANGES file I find:
--- 9.4.0a4 released ---
[...]
2006. [security]Allow-query-cache and allow-recursion now default
to the builtin acls localnets and localhost.
This is
Hello all,
If a the validation of a signed RR fails, the answer from the validating
resolver to the requestor is SERVFAIL, if I understood correctly. To the
average end user who isn't aware that DNS exists this translates to
it's broken. Possibly even my ISP is broken if the neighbor's ISP
does
I've got the idea!
So even I have no statement recursion yes, the server is still recursive
as time I dont specify recursion no;
It is going to make no difference if I'll add recursion yes; on options.
Is localnets a term I really need to use?
Currently I'm using an ACL defined for acl
Hi Gilles,
this question came up as well at a DNSSEC workshop I attended recently. IMHO
redirecting to a website will cause similar misuse to what wildcard records
have caused. One might argue a new RCODE would be the right thing but really,
the SERVFAIL is actually correct. The server at the
On 3/10/2010 4:45 PM, ic.nssip wrote:
I've got the idea!
So even I have no statement recursion yes, the server is still
recursive as time I dont specify recursion no;
It is going to make no difference if I'll add recursion yes; on
options.
No difference.
Is localnets a term I really need to
Additionally you can detect a DNSSEC failure by asking
queries with and without the CD bit set.
Most DNSSEC failures can be diagnosed with dig, knowing the
current time and date and access to named.conf for the trust
anchors. There are actually easier to
hi,
when i was in IPv4 environment test the dynamic update ,the result is
completely sucess,there is the result(rangi type is the new type i added):
[r...@localhost named]# host -t rangi 4086:0002:0010:::1
0001.0010.0002.4086.rangiid.arpa has RANGI record
16 matches
Mail list logo
