Re: difference in responses between UDP and TCP

> > If it is happening consistently, then it's possible that you have *two* >> DNS servers listening on the server, one on the UDP socket, and another >> on the TCP socket, and they're loaded with different zones. >> > > You are right, seems there are two DNS process listening TCP and UDP. :) >

Re: difference in responses between UDP and TCP

Hello Tony, > > Without knowing the server host name and zone name there could be lots of > different reasons, so there isn't really any way to answer. > > True, dig +tcp @212.26.18.3 pub.sa serial: 2017061804 dig +notcp @212.26.18.3 pub.sa serial:

Re: difference in responses between UDP and TCP

; on the TCP socket, and they're loaded with different zones. > To my understanding, they are running bind with one configuration. Will double check anyway. thanks, arun ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to

difference in responses between UDP and TCP

+short ns1.example.com. hostmaster.example.com. 2017061506 10800 3600 360 3600 any idea? thanks, -- arun ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org

How to keep the KSK private key offline with BIND dynamic signing?

/ Any ideas? -- arun ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users

Re: native pkcs#11 and dynamic signing issues

onfiguring zone keys # zone example.com/IN (signed): next key event: 24-Jan-2016 12:29:40.234 zone example.com/IN (signed): sending notifies (serial 2016012006) -- arun On Thu, Jan 21, 2016 at 1:08 PM, Arun N S wrote: > Thanks for the response. > > My understanding is that, when you us

Re: native pkcs#11 and dynamic signing issues

defined as "Engine: cGtjczExAA==" -- arun On Thu, Jan 21, 2016 at 1:01 PM, Tony Finch wrote: > Arun N S wrote: > > > > but with dynamic signing the logs were showing > > "dns_dnssec_findmatchingkeys: error reading key file > > Kexample.com.+008+01234.priv

native pkcs#11 and dynamic signing issues

xample.com.+008+01234.private: no engine dns_dnssec_findmatchingkeys: error reading key file Kexample.+008+05678.private: no engine zone example.com/IN (signed): next key event: 21-Jan-2016 13:36:59.184 any idea? Thanks, Arun ___ Please visit https://list

Re: dnssec-keyfromlabel-pkcs11 label format

My bad, there was a newline /n character at the pin file. -- View this message in context: http://bind-users-forum.2342410.n4.nabble.com/dnssec-keyfromlabel-pkcs11-label-format-tp1382p1413.html Sent from the Bind-Users forum mailing list archive at Nabble.com. _