Upstream has improved tooling (see [1]) plus claims that scripts
for automating this are readily available on the pdns-users mailing
list (and possibly in upstream git).
[1]
https://github.com/PowerDNS/pdns/commit/d978e1a5698165c38f819a64dbc41c0f7cc5dc33
--
,''`. Christian Hofstaedtler
: :'
forwarded #376036 https://github.com/PowerDNS/pdns/issues/467
thanks
signature.asc
Description: Message signed with OpenPGP using GPGMail
tags #376036 upstream
forwarded #376036 http://wiki.powerdns.com/trac/ticket/467
thanks
On Thu, Jun 29, 2006 at 11:22:43PM +0200, martin f krafft wrote:
> Especially on machines using supermasters, it would be awesome if
> pdns could run periodic checks on zones that it slaves and for which
> it h
FYI, this is what happens on the superslave if I remove a domain
from the master:
Aug 9 23:40:38 clegg pdns[1064]: Error trying to retrieve/refresh
'seanius.net': Remote nameserver reported error: RCODE=2
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f.
Package: pdns-server
Severity: wishlist
Especially on machines using supermasters, it would be awesome if
pdns could run periodic checks on zones that it slaves and for which
it has not received a notification in a configurable time, and
remove the ones for which the master returns an error. Then
5 matches
Mail list logo
