I am getting these errors because I have resolve turn on in both my
secondaries? I was not getting this until I did this and need this for
some testing over the next three days so that some testing can be done
with our dev and outsourced test team. Is there a way to block these
request that are no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Stussy wrote:
[...]
I am in North America. The IPv6 buildout in Europe and Asia is more
advanced.
My local ISP (South Korea) does not support IPv6 yet, so i'm using IPv6
address provided by Hurricane Electric located in the United States of
In message [EMAIL PROTECTED], Gilles Massen writes:
Stéphane,
On Thursday 06 November 2008 14:01, you wrote:
dig MX trstech.net
makes a SERVFAIL. (The BIND resolver is set to dnssec-validation yes
and uses the ISC DLV registry).
That seems to be the issue: trstech.net has an DLV
In message [EMAIL PROTECTED], Byung-Hee HWANG writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Stussy wrote:
[...]
I am in North America. The IPv6 buildout in Europe and Asia is more
advanced.
My local ISP (South Korea) does not support IPv6 yet, so i'm using IPv6
address
Stéphane,
On Thursday 06 November 2008 14:01, you wrote:
dig MX trstech.net
makes a SERVFAIL. (The BIND resolver is set to dnssec-validation yes
and uses the ISC DLV registry).
That seems to be the issue: trstech.net has an DLV entry. It kind of
illustrates that once you've gone the dnssec
At Sat, 8 Nov 2008 17:58:55 -0800,
Steve Koon [EMAIL PROTECTED] wrote:
Is there a way to retrieve (or log during request) the actual queries
that made up the count for the NXRRSET and NXDOMAIN statistics? I am
curious what record types and queries that could not be served by this
domain.
The
