<div dir="ltr">Hello, <br><br>Thanks for replying Brian, <br>If we disable the <a href="http://MOMO.COM">MOMO.COM</a> on DNS serveur firstly, <span style="color:rgb(80,0,80)">there will be an impact for the other domains we will migrate after ? <br><br>Regards<br>Sai </span></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 4 sept. 2019 à 11:35, Brian Candler <<a href="mailto:b.candler@pobox.com">b.candler@pobox.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_-2298781764723738265moz-cite-prefix">On 04/09/2019 10:05, seddik alaoui
ismaili wrote:<br>
</div>
<blockquote type="cite">The
purpose of this migration is also to migrate the others domains
that are managed by the same NS (NS1 and NS2). <br>
The question is the following, if we start by disabling the <a href="http://MOMO.COM" target="_blank">MOMO.COM</a>
zone on powerdns and deleting the A (GLUE) records on route53,
there will be an impact for the other domains we will migrate
after? Is it a good idea to do it before moving the other zones?<br>
Then for each domain that will move, we will delete the NS and
create the zone on route53 </blockquote>
<p>This isn't really a powerDNS question, but I'll answer briefly
anyway.</p>
<p>The glue records for NS1/<a href="http://2.MOMO.COM" target="_blank">2.MOMO.COM</a> are irrelevant here. When
you move <a href="http://momo.com" target="_blank">momo.com</a> to route53, you'll be assigned a new set of
nameservers, e.g.</p>
<p><a href="http://momo.com" target="_blank">momo.com</a>. 43200 IN NS <a href="http://ns-1143.awsdns-14.org" target="_blank">ns-1143.awsdns-14.org</a>.<br>
<a href="http://momo.com" target="_blank">momo.com</a>. 43200 IN NS <a href="http://ns-1944.awsdns-51.co.uk" target="_blank">ns-1944.awsdns-51.co.uk</a>.<br>
<a href="http://momo.com" target="_blank">momo.com</a>. 43200 IN NS <a href="http://ns-422.awsdns-52.com" target="_blank">ns-422.awsdns-52.com</a>.<br>
<a href="http://momo.com" target="_blank">momo.com</a>. 43200 IN NS <a href="http://ns-964.awsdns-56.net" target="_blank">ns-964.awsdns-56.net</a>.</p>
<p>Therefore, you change the set of nameservers to that list in the
registrar. ns1/<a href="http://2.momo.com" target="_blank">2.momo.com</a> are not used to serve <a href="http://momo.com" target="_blank">momo.com</a> any
more, and hence the glue records are no longer required.<br>
</p>
<p>Equally, this doesn't affect any other domains which are
remaining on ns1/<a href="http://2.momo.com" target="_blank">2.momo.com</a>, since ns1/<a href="http://2.momo.com" target="_blank">2.momo.com</a> will still
resolve to your nameserver IP addresses.<br>
</p>
<p>When you move those other domains to route53, you'll have to
change *their* list of nameservers too (and note: you may get a
*different* set of nameservers for each domain you move to
route53)</p>
<p>When you've finished the whole process, you can decommission
ns1/<a href="http://ns2.momo.com" target="_blank">ns2.momo.com</a><br>
</p>
<p>Regards,</p>
<p>Brian.</p>
<p>P.S. the domain "<a href="http://momo.com" target="_blank">momo.com</a>" is currently running on nameservers
"<a href="http://dante.enter.it" target="_blank">dante.enter.it</a>" and "<a href="http://dexter.enter.it" target="_blank">dexter.enter.it</a>"<br>
</p>
</div>
</blockquote></div>