[Pdns-users] BIND Primary, PowerDNS Secondaries....

[Mark Watts]

> On 7/28/06, Juergen Ilse <powerdns at usenet-verwaltung.de> wrote:
> > > I've got a couple of zones which are served by a BIND master (we've got
> > > some custom zone checking scripts) and PowerDNS slaves.
> > > This works great but we've still got to configure the slaves with the
> > > zone records.
> >
> > You may automate the adding of new zones, when you declare the master
> > as "supermaster" (look at the documentation). I think the deletion of
> > zones or the change of the primary Nameserver must still be done manu-
> > ally, but i think the use of "supermasters" can still be helpful.
> >
> > > Does anyone else do this, and if so, how to you manage the updating
> > > of the slave configs in a sensible fashion?
> >
> > I didn't tried that, but i think, that is maybe a partial solution of
> > the problem ...
>
> Setting up a Supermaster seems to be a good way to do the initial
> population of PowerDNS, but zones are not removed automatically; in
> fact even setting expire to a low number and then removing the zone
> from the Supermaster does not affect how the slave responds; it still
> responds to queries for that zone and keeps the data in the backend.

For the record, Supermasters works just fine with Bind as the Master and 
PowerDNS as the slave.

I've enables cascading deletes on the domain table so hopefully that'll help 
when removing zones.

Mark.

-- 
Mark Watts BSc RHCE MBCS
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services Group
GPG Public Key ID: 455420ED

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20060811/0b8b4234/attachment-0001.sig>