Added CloudFlare Nameservers to registar but they change and domain stops working

Hi there, i need some help because i’m not able to manually add a domain to Cloudflare.
I have a VPS with Plesk, but to use less resources i’m trying to use the registar DNS, dominios(dot)pt, and connect it to Cloudflare.
So i manually added a domain to Cloudflare and changed the nameservers to
betty.ns.Cloudflare.com
mitch.ns.Cloudflare.com

as asked by Cloudflare. When i add these nameservers to my registar they immediately change to
gina.ns.Cloudflare.com
bart.ns.Cloudflare.com

Is this normal? Because after a while my domain stops working as Cloudflare doesn’t see the nameserver changes :frowning:

I asked my registar dominios(dot)pt and they told me i had to solve the issue with Cloudflare…

Can someone help? Thanks

Probably the same issue as Nameservers aren´t being recognized

Your domain must be still connected with a different Cloudflare account. Do you have access to that one? The fact that you cant change your nameservers, respectively that they change back is definitely an issue with your registrar though and should never happen. I’d contact them again and ask them to forcibly change and keep the new nameservers.

@cloonan

Hi and thanks for answering, i had previously read that topic, but i decided to create my own.
Previously the site was added to Cloudflare via Plesk, but i had removed it before adding it manually again, and to another account.

But just to confirm, the nameservers shoudn’t change right? They should be the ones i added?

Can you switch back to the old account?

They should not. That apparently something your registrar does as it seems to believe you entered the wrong nameservers. If that is the case it is their fault.

I have sent a new ticket to the registar explaining what is happening, hope they can help, because i don’t see a way to fix this via Cloudflare dash panel…

I can access the old account on Cloudflare, but there is no domain associated with it.

I assume the old account has the nameservers bart and gina, right? If you added the domain back to your old account it should work out of the box.

1 Like

I have added the domain to see the nameservers associated, but thet are:
amanda.ns.Cloudflare.com
lee.ns.Cloudflare.com

I have deleted the domain from that account and went back to my registar to add the nameservers again (betty.ns.Cloudflare.com and mitch.ns.Cloudflare.com) and when i added them and saved, guess what, they changed to amanda.ns.Cloudflare.com and lee.ns.Cloudflare.com!!

So something is definitely wrong with the Cloudflare dash, because even after deleting the domain it stays somewhat associated with previous settings, and i think it shouldn’t… I know that this could be easily solved via registar (still waiting for an answer) or adding the domain to the first account, but all my domains are added to one account to ease the managing process, as you can imagine :wink:

What to do next? Thanks again!

Okay, we now have six nameservers but only two accounts. Something doesnt add up.

You said they changed back, right? Where is that? At your registrar? How would the Cloudflare control panel be involved then? Whats the domain in question?

The domain is happyhandmade(dot)pt

I’m only making changes to the nameservers on my registar control panel - dominios(dot)pt - they change there, after i add the ones i want and save, they change but not for the ones i want!

Let me resume whats happening:

  1. Added domain to Plesk and it created a new account for it - but since i don’t wan’t to use that, i deleted the domain from the Cloudflare account
  2. Added domain to my Cloudflare account and added the Cloudflare nameservers betty.ns.Cloudflare.com and mitch.ns.Cloudflare.com to my registar control panel, but when i save the nameservers on my registar control panel, they automatically changed to gina.ns.Cloudflare.com and bart.ns.Cloudflare.com
  3. Added the domain on the new account that Cloudflare previously created for the domain to see the nameservers. On that account they should be amanda.ns.Cloudflare.com and lee.ns.Cloudflare.com. Deleted the domain from that Cloudflare account
  4. Went to the registar control panel again and added betty.ns.Cloudflare.com and mitch.ns.Cloudflare.com again. Saved the settings, and the nameservers changed again, but this time to amanda.ns.Cloudflare.com and lee.ns.Cloudflare.com - these are the nameservers from the new account that Cloudflare initially created for the domain via Plesk

So i think there is something wrong with the Cloudflare Dash Panel, because even after i deleted the domain from the Cloudflare Dash Panel, it stays associated with those nameservers, or with the previously associated nameservers, as i’m unable to associate the domain with the Cloudflare nameservers i want!

Alright, the nameservers Cloudflare currently lists are amanda and lee. Are these the nameservers given in your new Cloudflare account or in the old one?

Amanda and lee are for the new account that Cloudflare created for the domain in Plesk.
My old account has betty and mitch - these are the ones i want to use as i want to manage the domain on this account

And if you switch to betty and mitch your registrar immediately falls back to amanda and lee?

I’d contact them and tell them you need to have betty and mitch and they should ensure they stay in place.

The issue is that i don’t want amanda and lee (new account). I want betty and mitch (old account)…

Sorry, thats what I meant. I edited my previous response.

Ok thanks, i already send that to them, however don’t you think there is something strange with the Cloudflare Dash Panel, since i’m not the only one with similar issues…
Or do you think this is mainly registar’s fault?

EDIT: I have an answer from the registar, they since Cloudflare manages the nameservers, Cloudflare should fix the existing NS records on the DNS zone.

And i kind of agree with them since i noticed the previous related strange behavior with registering Cloudflare nameservers - it seems they are connected to an account and stay fixed like that, as i’m unable to add it to other account even when deleting the domain from the other account!

Does this have a time limit, i mean, do the nameservers stay associated to the domain during an amount of time (72h maybe)? And only after that the domain is released to be able to add other nameservers from Cloudflare?

There is nothing to fix. Cloudflare gave you nameservers and all you need to do is enter these nameservers under your domain. It is your registrar who is apparently the troublemaker by not accepting them and arbitrarily reverting them back.

Hi there, i have phoned the support and they also couldn’t change the nameservers because they always return to the first attributed nameservers by Cloudflare.
I have made a technical validation of the domain with the nameserver on DNS.PT and here is the log:
betty nameserver

Resultado da avaliação: Informação técnica válida
Log da avaliação: ++++++++****

; <<>> DiG 9.11.2-P1 <<>> @betty.ns.Cloudflare.com happyhandmade.pt NS +norecurse +noadflag +nocookie
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36487
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;happyhandmade.pt.INNS

;; ANSWER SECTION:
happyhandmade.pt.86400INNSamanda.ns.Cloudflare.com.
happyhandmade.pt.86400INNSlee.ns.Cloudflare.com.

;; Query time: 3 msec
;; SERVER: 2400:cb00:2049:1::adf5:3a4b#53(2400:cb00:2049:1::adf5:3a4b)
;; WHEN: Wed Oct 17 10:28:44 WEST 2018
;; MSG SIZE rcvd: 101

++++++++****

; <<>> DiG 9.11.2-P1 <<>> @amanda.ns.Cloudflare.com. happyhandmade.pt NS +norecurse +noadflag +nocookie
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22038
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;happyhandmade.pt.INNS

;; ANSWER SECTION:
happyhandmade.pt.86400INNSamanda.ns.Cloudflare.com.
happyhandmade.pt.86400INNSlee.ns.Cloudflare.com.

;; Query time: 1 msec
;; SERVER: 2400:cb00:2049:1::adf5:3a3f#53(2400:cb00:2049:1::adf5:3a3f)
;; WHEN: Wed Oct 17 10:28:44 WEST 2018
;; MSG SIZE rcvd: 101

++++++++****

; <<>> DiG 9.11.2-P1 <<>> @lee.ns.Cloudflare.com. happyhandmade.pt NS +norecurse +noadflag +nocookie
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28043
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;happyhandmade.pt.INNS

;; ANSWER SECTION:
happyhandmade.pt.86400INNSamanda.ns.Cloudflare.com.
happyhandmade.pt.86400INNSlee.ns.Cloudflare.com.

;; Query time: 0 msec
;; SERVER: 2400:cb00:2049:1::adf5:3b81#53(2400:cb00:2049:1::adf5:3b81)
;; WHEN: Wed Oct 17 10:28:44 WEST 2018
;; MSG SIZE rcvd: 101

++++++++****|

mitch nameserver

Resultado da avaliação: Informação técnica válida
Log da avaliação: ++++++++****

; <<>> DiG 9.11.2-P1 <<>> @mitch.ns.Cloudflare.com happyhandmade.pt NS +norecurse +noadflag +nocookie
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13195
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;happyhandmade.pt.INNS

;; ANSWER SECTION:
happyhandmade.pt.86400INNSamanda.ns.Cloudflare.com.
happyhandmade.pt.86400INNSlee.ns.Cloudflare.com.

;; Query time: 1 msec
;; SERVER: 2400:cb00:2049:1::adf5:3bd0#53(2400:cb00:2049:1::adf5:3bd0)
;; WHEN: Wed Oct 17 10:40:15 WEST 2018
;; MSG SIZE rcvd: 101

++++++++****

; <<>> DiG 9.11.2-P1 <<>> @amanda.ns.Cloudflare.com. happyhandmade.pt NS +norecurse +noadflag +nocookie
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30734
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;happyhandmade.pt.INNS

;; ANSWER SECTION:
happyhandmade.pt.86400INNSamanda.ns.Cloudflare.com.
happyhandmade.pt.86400INNSlee.ns.Cloudflare.com.

;; Query time: 1 msec
;; SERVER: 2400:cb00:2049:1::adf5:3a3f#53(2400:cb00:2049:1::adf5:3a3f)
;; WHEN: Wed Oct 17 10:40:15 WEST 2018
;; MSG SIZE rcvd: 101

++++++++****

; <<>> DiG 9.11.2-P1 <<>> @lee.ns.Cloudflare.com. happyhandmade.pt NS +norecurse +noadflag +nocookie
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39429
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;happyhandmade.pt.INNS

;; ANSWER SECTION:
happyhandmade.pt.86400INNSamanda.ns.Cloudflare.com.
happyhandmade.pt.86400INNSlee.ns.Cloudflare.com.

;; Query time: 1 msec
;; SERVER: 2400:cb00:2049:1::adf5:3b81#53(2400:cb00:2049:1::adf5:3b81)
;; WHEN: Wed Oct 17 10:40:15 WEST 2018
;; MSG SIZE rcvd: 101

++++++++****|

As you can see, the domain is validated correctly with the nameserver betty, however it always returns the old nameservers amanda and lee.
.PT domains are “special” domains with “special” rules, but as i can see, Cloudflare DNS is correctly supported by those rules, however in this case Cloudflare has to remove the associated amanda and lee nameservers from this domain so that i can successfully add the domains i want.

That is a - sorry - rubbish explanation by them, as they can enter whatever they want. It is completely irrelevant what Cloudflare returns. They are the authoritative place for .pt and should simply enter what you told them.

They will, the moment the domain has been properly verified by the .pt authority but for that it is necessary to list the desired nameservers in the .pt registry. That is a bit of a chicken/egg dilemma but the registry/registrar could easily fix that.

1 Like

Well i don’t really know what to do next, the registar says they can’t do it, and although i thank you a lot for your help, i can’t seem to fix this issue with Cloudflare either.

What should i do next? Is it possible to send this issue to Cloudflare support team so that they can help me? Or the registar is the only one that can solve this?

You can only contact Cloudflare’s support. Maybe they have a solution, but generally it would be really up to the registrar to fix this. The problem here is their artificial obstacle.