My understanding from the ARM is that the dnssec-policy can be in the
"options", "view" or "zone". I have mine in "view" and when I try to move
into "options" I get a syntax error that I cannot seem to understand what
is wrong. I stripped out all other statements and reduced the
dnssec-policy to
As if DNSSec is not confusing enough...It seems the ARM manual that matches
my release is out of step with the web site. I followed the "Easy-Start
Guide for Signing Authoritative Zones" in the ARM manual after manually
signing my test zone for my starting point. The ARM says you ONLY need to
If you visit https://bind9.readthedocs.io/en/v9.18.15/ you will see a menu
in the lower left corner where you can select older releases of the bind
ARM manual. But those links do not work and return a 404. Should those
links work? Or do they need to be removed?
In my case I visited
I am planning on implementing the current version of BIND to replace the
aging, undocumented authoritative servers I inherited. I want to hide the
primary server on our internal network and have two secondary servers be
publicly available. While reading the DNSSEC Guide
Bruce, I would push back and ask for more information from whomever is
leading you down that path as it does not sound right to me although others
more familiar with DNS magic might have better suggestions to DNS changes.
But if Barracuda is just a front-end for email that does antivirus/spam
New to BIND and just starting to read the 5th edition from O'Reilly after
watching some videos online while it made its way to me. I am trying to
understand why the view statement appears to be included by default in most
Linux distributions if best practice says you should have separate servers
6 matches
Mail list logo
