> I noticed in oracle backed schema SQL, there isn't any master > nameserver column available in Zones table.
> I can specify zone type, but not master name server if type is > set to slave. That is correct. "Works as designed." SQL> desc zones Name Null? Type ----------------------------------------- -------- ---------------------------- ID NOT NULL NUMBER(38) NAME NOT NULL VARCHAR2(512) TYPE NOT NULL VARCHAR2(32) LAST_CHECK NUMBER(38) REFRESH NUMBER(38) SERIAL NOT NULL NUMBER(38) NOTIFIED_SERIAL NUMBER(38) SQL> SELECT type FROM zones; TYPE -------------------------------- MASTER The reason for this that the documentation recommends slaving be implemented via database replication. However, one can also configure replication via the traditional AXFR. If one configures replication via AXFR, "master" and "slave" is driven by "master=yes" and "slave=yes" in pdns.conf(4), where a server can be both a master and a slave at the same time. The way to distinguish a master from the slave is the SOA record in the records table. The slave will have a type of "NS", but no SOA record. AXFR is triggered by atomically updating the serial number in records.content WHERE type = 'SOA' and in the corresponding zones.serial. I too have a zonemasters table, but it is empty. I never did fig- ure out what it was for, but as it turns out, it does not appear to be required for normal master-slave operation. SQL> SELECT * FROM zonemasters; no rows selected _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
