The slave servers obtain zone data via a process called zone transfer (AXFR) or incremental zone transfer (IXFR).(And I refuse to abstain from using the terms master/slave.) When we provision a master server with a new zone we must update all slave servers and inform them of the existence of this new zone and which addresses the master servers for the zone have.
Note also, that this is currently very simplistic and needs quite a bit of refinement, which I’ll probably do soon-ish.
The (hidden) master servers have to be able to NOTIFY a separate server: 1. Queued also-notification of domain 'b.aa' to 1.153 5.
Power DNS also includes a webserver (commented out of the pdns.local file above).
If enabled, you can visit it via (I accessed it via SSH port forwarding, since I wasn't on the machine I was testing).
above), there is always some time lag (sometimes several minutes) until the new zone(s) is (are) available on the BIND slave servers.
I’ve given this some thought, particularly in view of the fact that BIND has addzone and NSD4 also has support for addzone, allowing both brands of servers to configure new zones on-the-fly.
Unless you are using Power DNS with My SQL or Postgre SQL replication (which is off topic for this discussion) this is a procedure that is normally done manually.
By manually I mean there is no standard procedure for doing this.
The Power DNS Nameserver is a modern, advanced and high performance authoritative-only nameserver.