Re: problem validate key of isc dlv

2011-03-21 Thread Torinthiel
On 03/21/11 02:13, fakessh @ wrote: Yes, I bothered to redeploy new keys, fields TXT, a new signature. and more on a new rehabilitation isc dlv. I still get the same error nb : Simply debuggers dnssec still provide all kinds of resultasts And that's probably the main problem. Two of

Re: problem validate key of isc dlv

2011-03-21 Thread fakessh @
I managed to walk isc dlv with only 2 servers with active dnssec above. and I quote ns1.novacrea.fr and ns1.xname.org. it produced no problem before Le lundi 21 mars 2011 à 07:45 +0100, Torinthiel a écrit : On 03/21/11 02:13, fakessh @ wrote: Yes, I bothered to redeploy new keys, fields

Re: Need help on DNS reporter

2011-03-21 Thread babu dheen
Hi,   Actually i am looking for open source software which can be installed on redhat linux BIND server to geneerate report from the DNS logs.   Regards Papdheen M --- On Sun, 20/3/11, Warren Kumari war...@kumari.net wrote: From: Warren Kumari war...@kumari.net Subject: Re: Need help on DNS

Not Exact error

2011-03-21 Thread Davenport, Steve M
Can someone tell me the cause of the not exact error and how to troubleshoot? 21-Mar-2011 11:01:24.931 xfer-in: error: transfer of '219.130.IN-ADDR.ARPA/IN' from 130.219.31.5#53: failed while receiving responses: not exact After this message appears, a retry on the transfer runs error free.

Re: Need help on DNS reporter

2011-03-21 Thread wllarso.dns
What's more open source than a one line shell script? It is too simple to spend the time packaging it for rh linux. Try running this against your query logs to see if it does what you want then tweak it as needed. If all else fails look at DNSTOP. Simple single purpose tool that may fit your

Re: Not Exact error

2011-03-21 Thread Mark Andrews
In message f7c01ac623c2bd48a4b5a1e91ba1dc562456c33...@2008mbx.utmck.edu, Dav enport, Steve M writes: Can someone tell me the cause of the not exact error and how to troublesh= oot? 21-Mar-2011 11:01:24.931 xfer-in: error: transfer of '219.130.IN-ADDR.ARPA/= IN' from 130.219.31.5#53: failed