On Mon, 01 Nov 2010 15:51:59 -0500, Curtis Maurand <[email protected]>
wrote:
See the supermaster/slave documentation. Create the zone on the
supermaster, it gets created on the slave. Make a change on the
supermaster, it propagates the change to the slave. The only thing it
doesn't do, is delete a zone.
I don't quite think you understand the situation we're describing, or
perhaps you're describing a method that I misunderstand --
We host hundreds of domains that are like foo.com, foo.net, foo.org, etc.
If a customer who owns all of these wants to update the www record, we
would have to make this change multiple times. With BIND and using the
file backend (or pdns perhaps), we can just symlink zone files so they all
have the same values. This is what we're trying to achieve, but put the
backend in a database and be able to use a web interface to manage it.
One customer has about 300 domains that all have the same values... We
really don't want to have to update every single one by hand or craft
custom SQL each time we need to do something like this. It should be easy
to "group" or "link" domains that should all keep the same values.
Regards,
Mark
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
