[Pdns-users] Notification for domains to ip1:53 failed after retries
steve.zeng at booking.com
Mon Jan 15 13:41:51 UTC 2018
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 a DNS change. further investigation shows that the delay seems on PowerDNS. we see lots of errors
2018-01-10T18:13:24.728722+01:00 pdns_server1 pdns_server: Jan 10 18:13:24 Notification for example.com to ip1:53 failed after retries
2018-01-10T18:13:24.728848+01:00 pdns_server1 pdns_server: Jan 10 18:13:24 Notification for example.com to ip2:53 failed after retries
2018-01-10T18:13:24.728975+01:00 pdns_server1 pdns_server: Jan 10 18:13:24 Notification for example.com to ip3:53 failed after retries
ip1,ip2,ip3 are BIND slaves.
no other errors found with regard to the root cause. it happens occasionally. Questions are:
1. Is there any rate limit as far as PowerDNS is concerned? before PowerDNS is put in the middle, there is no such delay
2. Is it configurable to set how many retries? Should PowerDNS should ensure the notifications going through rather than drop after a certain times of retry?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pdns-users