<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 04/09/2019 10:50, seddik alaoui
ismaili wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGxt3+pS96NrfoYNZmrvrziHVUD4vFv58hbBQUJ1M4R8HvaSQw@mail.gmail.com">If
we disable the <a href="http://MOMO.COM" moz-do-not-send="true">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 ? </span></blockquote>
<p>First, you create MOMO.COM on route53, with identical zone
contents.<br>
</p>
<p>Then you change the registrar to point to route53's nameservers.</p>
<p>Then you wait for at least 48 hours. At this point, no queries
for *.MOMO.COM (including NS1.MOMO.COM/NS2.MOMO.COM) should be
arriving at your nameservers.</p>
<p>Then you could delete MOMO.COM from our own nameservers if you
wish - or you can just leave it there, it doesn't matter.<br>
</p>
<p>At this point, any other domains which use NS1/2.MOMO.COM will
still be working as before. They will still be delegated to
NS1/2.MOMO.COM. DNS lookups to resolve NS1/2.MOMO.COM to A/AAAA
records will still work - those lookups will be querying route53's
nameservers. But the actual queries for those other domains will
still arrive at NS1/2.MOMO.COM</p>
<p>The important thing is: when you create the MOMO.COM domain on
route53, don't change the contents. Most importantly, leave
NS1/2.MOMO.COM pointing to your existing powerDNS servers - since
your other domains depend on being able to resolve NS1/2.MOMO.COM.<br>
</p>
</body>
</html>