Transfer domain from PlusNet to Cloudflare - need to update nameservers

[#1]

I want to transfer a .co.uk domain that is currently hosted with PlusNet to Cloudflare.

Their process requires the nameservers for the domain to be updated to Cloudflare's nameservers BEFORE the IPS tag is updated.

PlusNet support are saying they can't update NS records, and they can only update the IPS tag.

How can I get the NS records for my domain updated?

Cloudflare says:

"Warning

If you request your current registrar to update the IPS tag before completing the checkout process, the transfer request will be automatically rejected. You must complete the checkout process before requesting the IPS tag update."
I can't complete checkout until the NS records point to Cloudflare's DNS servers.

[#2]

It's not possible to change the nameservers on a Plusnet hosted domain.

Cloudfares procedure is unusual. Normally you just change the IPSTAG first and the new registrar accepts the domain. You then configure the new providers nameservers to match the old ones and then finally switch them

[#3]

Thanks for replying.

PlusNet is unusual as a hosting provider for limiting my control to only A, CNAME and MX records.  I can't even add an SPF record or TXT record, which is a very common thing when linking your website up with cloud services.

Cloudflare's process makes a lot of sense both for security and getting it right without service interruption.  And other registrars let me update all my DNS records (it's my domain after all), so it's not an issue.

PlusNet manage my DNS records, so somebody in PlusNet is able to update them.  I just need to find out how to get in touch with the right team.  The support desk don't know.

[#4]

PlusNet is unusual as a hosting provider for limiting my control to only A, CNAME and MX records.

@imagesofafrica Im aware of that, I used to have a domain hosted at Plusnet.

PlusNet manage my DNS records, so somebody in PlusNet is able to update them. 

Whilst that is undoubtably true, there is no process to get them changed and as I said earlier its mandatory that a domain hosted by Plusnet MUST use their nameservers.

Cloudflare's process makes a lot of sense both for security and getting it right without service interruption.

I'm not sure it does! Transferring a domain registration should not affect the namservers. Nameserver records are subject to a 24h TTL and so to effect a no-downtime transfer you must be able to have set the new provider DNS to match the existing before changing nameservers.

[#5]

Cloudflate’s approach is very unusual. With any domain name transfer I have ALWAYS changed the ISPTAG first, leaving the domain pointing at the same name server.

That then allows configuration of the new DNS before doing the switch. It also allows the TTL on the name server to be reduced. Changing the NS without reducing the TTL could result in the domain names being unresolvable.

I’ve used several hosting providers … your reported experience here will ensure I never use Cloudflare. I’ve moved domains very swiftly using both LCN.com and Mythic Beasts.

[#6]

Hi @imagesofafrica 

We can get this organised for you but we'll need the details of the nameservers along with your account details

I'll drop you a PM shortly so we can get this organised

[#7]

@MatthewWheeler but won't changing the nameservers immediately 'break' any Plusnet hosting of the domain ?

[#8]

@MatthewWheeler That would be great, thanks.

I look forward to hearing from you

[#9]

---

@MisterW wrote:

@MatthewWheeler but won't changing the nameservers immediately 'break' any Plusnet hosting of the domain ?

---

I guess that depends on what you mean by "break".

Certainly if the new DNS server and the target services are not built and configured BEFORE the NS is changed (which seems like the way this is heading) there will be a period during which anyone looking up the domain will find that it cannot be found.

To me, this approach is not logical and risks a period of the domain name being unresolvable or there being no service to connect to.  Whatever, they way this is done should be a choice of the user, not something dictated by the provider.

On EVERY occasion I have moved hosting, I have established the new host services and the the new DNS configuration BEFORE switching name servers.  Making that the last step ensures that there is always a 'working target' for the domain.  There might still be an interval (as defined by the TTL) during which name resolution could point to either the new or the old hosts, until the TTL for the old host has expired, but never a period where there is nowhere to route connections.

[#10]

Cloudflare deals with this by copying the existing DNS records from PlusNet / other host and so they already exist.

When PlusNet change the nameservers to Cloudflare, then Cloudflare will immediately be able to respond to DNS requests with the same responses that PlusNet DNS servers would give.

From this point I can add/change DNS entries in Cloudflare.

Once Cloudflare realises this has happened, then the IPS-TAG can be changed and the SOA updated.

[#11]

@Townman 

I guess that depends on what you mean by "break".

My understanding, and ICBW, is that you can't host email or a website on Plusnet using third party nameservers. So even if the third party DNS is configured to point to, for example, the Plusnet mail servers it won't accept email.

[#12]

@MisterW 

I was thinking similar, but was not certain.  The other considerations are very predictable, even if the existing DNS entries are cloned.

I guess that there are two approaches here: if you know what you are doing, then you'd probably want to do it yourself as described above and as you have done; if you do not know how to do it, you'd want someone else to do it for you ... in which case what happens, just happens!

Hope there are no tears before bedtime for @imagesofafrica - stunning pictures BTW.  What are you going to use for your new website?  Wordpress?  It has some great tools for delivering photographic galleries / picture 'books' ... some of the free ones are amazingly good.