Brian and Bert - thank you both for the analysis and sanity check. I'll
continue to focus on the network between me and the affected name server.
On Tue, Jan 23, 2018 at 2:28 PM, bert hubert
wrote:
> Hi Brian,
>
> On Tue, Jan 23, 2018 at 02:00:58PM -0700, Brian T wrote:
> > My recursor config h
On 25/01/2018 16:50, Alain RICHARD wrote:
Also about your example of a customer move the domain to an other, I
don’t think this is solve by the separation of recursor and auth
server as you will have to remove the forwarding zones from the
recursor and/or the dnsdist processes in order to corre
Hi Brian,
I completly agree with you that it make sense for medium to large ISP needs to
separate resolver from auth servers for several reasons.
My point was that the powerdns architecture and its good API make it a very
interesting for small ISP or small to medium size enterprises : you may h
On 25/01/2018 10:08, Tom Ivar Helbekkmo wrote:
I found these two blog postings useful:
https://blog.powerdns.com/2016/01/19/efficient-optional-filtering-of-domains-in-recursor-4-0-0/
https://blog.powerdns.com/2016/06/28/response-policy-zone-support-in-powerdns-recursor/
And this presentation:
Pieter Lexis writes:
> Moreover, the DNSBL experience can also be approximated by using the Lua
> scripting functionality in the Recursor[2] to block queries based on a
> loaded list.
> [...]
> 1 - https://doc.powerdns.com/recursor/lua-config/rpz.html
> 2 - https://doc.powerdns.com/recursor/lua-s
Hi Steve,
On Wed, 24 Jan 2018 14:00:59 -0800
Steve Zeng wrote:
> speaking of slaves, does PowerDNS Recursor can fully replace BIND in your
> experience? i.e. forwarding, caching and DNSBL, etc.?
The answer is "yes". The Recursor supports forwarding (both recursive
and non-recursive) and RPZ[1
