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
> On Jan 17, 2018, at 4:26 PM, Klaus Darilion
> wrote:
>
> Yes. Immediately right after.
Great to know that. our delay period was about 5-6min and that concerns me.
>
> I just re-read your log lines:
>
10-Jan-2018 18:11:24.387 notify: client 10.198.180.41#12149:
> received notify for z
Arsen,
My PowerDNS is a slave, it is then send notifications to quite a few other
slaves. So it is a chain. it is noticed that the delay is between PowerDNS
(first tier slave) and BIND slaves (second layer slave).
The PowerDNS settings are below, based on
https://github.com/PowerDNS/pdns/issu
Am 17.01.2018 um 15:13 schrieb Steve Zeng:
> Pieter,
>
> I checked BIND slaves logs around the time frame and found:
>
> 10-Jan-2018 18:11:17.211 notify: client 10.198.180.41#12149: received notify
> for zone 'example.com'
> 10-Jan-2018 18:11:17.211 general: zone lhr4.dqs.booking.com/IN: notif
Pieter,
I checked BIND slaves logs around the time frame and found:
10-Jan-2018 18:11:17.211 notify: client 10.198.180.41#12149: received notify
for zone 'example.com'
10-Jan-2018 18:11:17.211 general: zone lhr4.dqs.booking.com/IN: notify from
10.198.180.41#12149: no serial
10-Jan-2018 18:11:24
Hi Steve,
On Mon, 15 Jan 2018 14:41:51 +0100
Steve Zeng wrote:
> we are migrating our DNS master from BIND to PowerDNS. The approach we take
> is to put PowerDNS in the middle of an current replication chain as below:
>
> BIND DNS master -> PowerDNS -> BIND DNS slaves
>
> It works most of the
Hi,
we are migrating our DNS master from BIND to PowerDNS. The approach we take is
to put PowerDNS in the middle of an current replication chain as below:
BIND DNS master -> PowerDNS -> BIND DNS slaves
It works most of the time. However, from time to time we experienced long delay
when making
