I'm interested in the "view forwarding" method. I'm only setting up views
to resolve a split DNS issue with one domain. I'd like to have that one
zone/domain in my internal view and then if the source IP requests info for
any other zone forward that to my external view. To me this sounds like a
who
On Tue, Sep 6, 2016 at 1:39 AM, Dave Warren wrote:
> On Mon, Sep 5, 2016, at 09:46, John Levine wrote:
> > >1. pick a primary domain from the list of virtual hosts (example2.com)
> > >2. use the "real" host name of the server (juvat.example1.com)
> > >3. the mail server name (mail.example1.com
Hi list,
From "https://kb.isc.org/getAttach/21/AA-00512/rpz.txt";, Chapter 3 -
Subscriber Behavior:
...
...
If a policy trigger results in a modified answer, then that modified
answer will include in its "authority" section the SOA RR of the DNS RPZ
whose policy was used to generate the modi
Hi Mukund
Many thanks for your hint. In fact named was compiled with
"--enable-querytrace". After recompiling 9.10.4-P2 without querytrace,
the log looks good.
Kind regards,
Tom
On 09/06/2016 09:32 AM, Mukund Sivaraman wrote:
Hi Tom
On Tue, Sep 06, 2016 at 07:37:50AM +0200, Tom wrote:
I
Hi Tom
On Tue, Sep 06, 2016 at 07:37:50AM +0200, Tom wrote:
> Is there a workaround/configuration-directive not to log every request with
> this "error"? One way would be using BIND 9.9.9-P2 (because this code was
> added in 9.10.x...), but I would prefer 9.10.x.
(1) Don't use regular BIND 9.9 fo
5 matches
Mail list logo
