The ns record not work when transfered to cloudflare

I transfered my domain to Cloudflare, but before I transfer to Cloudflare, my domain’s Name Server Record(NS Records) were not point to Cloudflare. after the transfer, the Name Server Records keeps the old ones, and I also can’t change them in Cloudflare. what should I do?

I try to remove the domain and add again. but when I removed the domain, I can not add again. it show me the domain is banned. (

I deleted the domain from Cloudflare, but it also deleted from registar, how can I get the domain back?

If we are talking about Cloudflare’s Registrar product it allows you to transfer a domain only if it active on Cloudflare, so with correctly set Cloudflare Name Servers. I can’t think of a way to do it differently.

If we aren’t then there is no way deleting a domain from the dashboard (especially if not set-up with Cloudflare Name Servers) would cause issues. In particular there are no possible way where Cloudflare deleted the domain from the registrar.

The banned domain could be due to the fact that you added and deleted it multiple times. For that you should contact support (last option under support in the dashboard).

A WHOIS lookup shows me Name’s Name Servers:

my problem happens as follows:

  1. my domain’s old registar is, and the domain was active at Cloudflare(as NS used to be Cloudflare);
  2. my domain expired at and need to be renewed, so the Name Server automatically changed to, but this domain still active at Cloudflare, and I can transfer it from to Cloudflare,
    and I did that transfer.
  3. I found that the Name Server still be, and the Cloudflare DNS not works.
  4. I tried to delete and readd the domain to Cloudflare, and can’t add it to Cloudflare again.
    finally, the domain is lost, not in, can’t be found at Cloudflare.

I think the issue here was transferring after the domain expired, in that moment the NS changed at making Cloudflare fail.

Calling @SamRhea here, probably best!

I would recommend trying to contact Name’s support though, they should be able to let you register that domain again, unless, you can simply register it again there as normal. Then you activate it again on Cloudflare with the help of support (to remove the ban) and then after the 60 days of block imposed by ICANN you transfer it here. Note that each time you transfer you add the about you pay for at the end of the term, so you won’t lose anything transferring before the expiration.

The domain still is registered and appears to be functional with Cloudflare as registrar. The only problem seems to be it is not associated with the account but support should be able to fix that easily and also re-set the nameservers properly to elsa and walt.

Thanks @sandro, didn’t think of looking a few lines above. My call to Sam was correct then, he is the one to call here including support, but I imagine they don’t have the ability to change name servers since it’s not a possibility in the dashboard.

Right now, Cloudflare does not permit domains registered through them to point anywhere else, so I guess thats why they omitted that option to begin with. Being the registrar however, they should be able to make that change themselves with the registry. I guess :smile:

They only might require an official request from the OP to officialise it but thats formalities :slight_smile:

Oh I know that, it was simply stating that missing that option from the dashboard I don’t know how many other controls they have compared to a simple user unless they go to supervisors or something…

I’d hope support would have a vastly larger set of options :smile: and if they had to go down to the much dreaded CLI :wink:

how can I contact @SamRhea to restore my deleted domain? there’s no support tickect system at Cloudflare.

There is, follow @sandro’s link or what I told you before, last option under support in the dashboard.

Hi @sandro - we’ve seen this happen once before. It’s a frustrating aspect of how some registrars handle transfers and expirations (if I’m reading this correctly).

  1. You started your transfer to Cloudflare with your Cloudflare nameservers
  2. When the domain expired, Name{.}com forcibly modified your nameservers to “seize” it, but allowed the transfer to complete
  3. When you transfer to Cloudflare, we kept your now-seized nameservers.

We do have a method to change nameservers in an emergency. Could you open a support ticket with the link that @sandro sent and we’ll validate the request and make the changes immediately? Sorry that your previous registrar made this change at a very inconvenient time.

1 Like

You should mention @sham :wink:

It seems that the similar thing is also happening to me.
my domain name was not expired, I just transfer it from previous registrar.

  1. My domain is active status in Cloudflare.
  2. Before I transfer the domain name, I modified the NS to the NS the previous registrar provided.
  3. I do the transfer.
  4. After transfer, the NS records still old. not the NS of Cloudflare.

my ticket is 1615789. thank you.

Thanks - looks like your previous registrar hijacked the NS in some way during the transfer - there are a few other reasons, beyond just expiration, they can do that. We’ve also seen it done for a lack of email verification, for example.

We will never touch the NS during a transfer: when the transfer completes, the NS you have in that moment will be the ones you have on Cloudflare.

We can still help you out to fix this; thanks for flagging the support ticket. We’ll get it evaluated.


The similar problems happens to me also.
Since my domain name is expired in the old registrar, I have moved the domain to Cloudflare registrar.
But after I have transferred my domain, the namservers did not change to the Cloudflare ones, it remains to be with the old registrar’s expired nameservers.

I could not find any options to configure the nameservers in the Cloudflare dashboard.

My ticket number is [1616302] and my website cannot be reached now.

Thank you for your help!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.