Hi, To fix this problem, you don't have to add your ns4 to the NS records.
*use the pdnssec utility:* pdnssec rectify-zone test.com And the ns1, ns2, ns3 will initiate the transfer from ns4 :) *Here an example:* % Jul 05 10:34:13 Received NOTIFY for test1.com from xxx.xxx.xxx.xxx for which we are not authoritative Jul 05 10:34:13 Unable to find backend willing to host test1.com for potential supermaster xxx.xxx.xxx.xxx *Solution*: Execute the following command (utility): *pdnssec rectify-zone test1.com* *Result: * % Jul 05 10:38:26 Received NOTIFY for test1.com from xxx.xxx.xxx.xxx for which we are not authoritative Jul 05 10:38:26 Created new slave zone 'test1.com' from supermaster xxx.xxx.xxx.xxx, queued axfr Jul 05 10:38:26 Initiating transfer of 'test1.com' from remote 'xxx.xxx.xxx.xxx' Jul 05 10:38:26 gmysql Connection successful Cheers :) Mohamed -- View this message in context: http://powerdns.13854.n7.nabble.com/Supermaster-Slaves-Supermaster-has-to-be-a-listed-NS-tp9276p10148.html Sent from the PowerDNS mailing list archive at Nabble.com. _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
