[Pdns-users] Supermaster & Slaves - Supermaster has to be a listed NS?

[Aki Tuomi]

On Fri, Jul 05, 2013 at 01:58:40AM -0700, ymicromed wrote:
> 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
>

This will not cause domain transfers, sorry :(
 
If you want to have your domain notified to ns4, please add it as 'ALSO-NOTIFY'
in domain metadata.

> 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: *
> 

This is because you have supermaster on and master notified you. it had nothing
to do with rectify-zone commands. 

> % 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
>

Aki Tuomi 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20130705/fb0f944e/attachment-0001.sig>