On 20.09.12 19:49, Oscar Ricardo Silva wrote:
The current servers are configured to forward any queries for our
domain straight to our authoritative servers:
I've been reading about the new zone type: static-stub and believe
this may work better for us.
If I'm correct, it will send
BIND 9.7.7, 9.8.4 and 9.9.2 have improved OpenSSL error logging.
Unfortunately, our logs are now filling up with RSA_verify failed
messages.
Yeah, oops, we made that one too noisy. You're not the first one
who's noticed. :/
How does one go about tracking down the source of these failures
On 10/10/12 9:41 PM, Árni Birgisson wrote:
You have all those allow-*, but in your previous email you have
recursion no; which you would have to change to recursion yes;.
When you have done this, make sure to restrict it with the allow-recursion
so you do not have an open resolver.
On 10/10/12 20:52, kalin wrote:
On 10/10/12 9:41 PM, Árni Birgisson wrote:
You have all those allow-*, but in your previous email you have
recursion no; which you would have to change to recursion yes;.
When you have done this, make sure to restrict it with the
allow-recursion
so you do
Make sure you are editing the named.conf named is using. Change
the version string, reload the server and check that the version
reported matches what is in named.conf.
If that doesn't identify/fix the problem post, to the list, the
complete named.conf along with any included files (x out the
On 10/10/12 10:17 PM, Lyle Giese wrote:
On 10/10/12 20:52, kalin wrote:
On 10/10/12 9:41 PM, Árni Birgisson wrote:
You have all those allow-*, but in your previous email you have
recursion no; which you would have to change to recursion yes;.
When you have done this, make sure to
On Oct 10, 2012, at 7:22 PM, kalin wrote:
if i add a zone record to the named.conf i'm editing and do a dig on it,
locally i get it fine:
$ dig @ns2. domain.com
; DiG 9.8.1-P1 @ns2. domain.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode:
7 matches
Mail list logo
