I had added new CF nameservers onto AWS registrar and it had been more than 24 hours.
My CF overview still stuck at Pending Nameserver Update.
“whois justswap.link” is reflecting the nameserver
whois justswap.link | grep “Name Server”
Name Server: melany.ns.cloudflare.*
Name Server: brady.ns.cloudflare.*
dig ns justswap.link +short
brady.ns.cloudflare.*
melany.ns.cloudflare.*
Seems to me that the registrar has already applied the nameserver changes but CF is still stuck.
You have four Cloudflare nameservers listed, when you must not set any others than those assigned in your account. Update the nameservers at your registrar and once set correctly Cloudflare can verify it.
the other 2 nameservers also have active and valid DNS record.
does that mean, we can only have 2 nameservers active at any point of time?
the situation is in current status, we are trying to migrate from an old CF account to new CF account.
all in mind that we maintain 100% service reachability.
was thinking to add the 2 new nameserver to registrar and test first, then follow by removing the 2 old nameserver.
is there a better way to implement it so that we will not risk any chance of service reachability during the transmission of nameserver update?
Yes, as mentioned that does not work.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.