Jump to content

[HH#489225] Cloudflare Registrar and Addon Domain Validation


Recommended Posts

Posted

Username: N/A, Server: N/A, Main Domain: N/A

 

Hello,

My user is p1xl and my domain is elmandadoccs.com

 

I'm trying to setup this domain with Cloudflare SSL and noticed that they

now have a Registrar service, so I purchased my new domain through them.

The problem is that for some reason they don't let you change the

nameservers for the domain like with every other registrar I've ever worked

with.

 

I contacted Cloudflare to help me change the nameservers momentarily to

ns1.heliohost.org and ns2.heliohost.org and this was their reply:

 

*The short answer is that Cloudflare Registrar only uses Cloudflare name

servers. For now.If your hosting has cPanel, I'm surprised they have that

restriction, as many people here use cPanel. I suspect they deliberately

configured it that way.If they won't cooperate, your only choices are to

either wait out the 60 day transfer hold and move your registration

elsewhere, or host your site somewhere else right now.*

 

As you can imagine, waiting 60 days is not an option and I really want to

give Heliohost a try, so what other forms of validation can I use?

 

Most hostings give you an option to create a CNAME or TXT entry which I

could easily do in Cloudflare's DNS.

 

I really wish I had known this beforehand and simply purchase the domain

though Namesilo :-(

 

PLEASE give me a hand with this!

 

PS: I read on the forums that if I change my Primary Domain with the

script, it should work. I did that last night but it's still not working.

 

Many thanks in advance!

Posted

You can make the website itself work by making the domain your account's main domain and setting an A record on CF pointed to the server's shared IP. You'll probably also want to create an MX pointed to the same, and a TXT specifying an appropriate SPF (there's sites online to help you generate one) so you can receive email.

 

Please be aware though that email DKIM, webdisk, addon domains, subdomains, aliases, DNS, AutoSSL (for accounts on a server that's not Johnny) and numerous other features will NOT function in this configuration. For full functionality, you'll need to transfer the domain to a proper registrar and use our name servers.

 

Also, please keep in mind that we do not support any account or domain that does not use our name servers, so we will be unable to provide support for your account if you choose to use it in this configuration.

 

I'm not sure why CF says it's an uncommon requirement to require you use the host's name servers, it's actually the default configuration in cPanel, and a major security risk to allow otherwise (requiring the NS change is how we make you prove you own the domain).

Posted

I understand that this is not a common problem since every other registrar

I know lets you change the nameservers for your domains. Maybe Cloudflare

Registrar will allow this in the future.

 

Yesterday I created the A record on Cloudflare's DNS pointing to the

HelioHost server (Ricky) shared IP. I guess it's a matter of waiting a bit

longer before somebody finishes setting it up.

 

Thank you for your help!

 

On Mon, Aug 3, 2020 at 7:18 PM Heliohost Support

wrote:

 

> You can make the website itself work by making the domain your account's

> main domain and setting an A record on CF pointed to the server's shared

> IP. You'll probably also want to create an MX pointed to the same, and a

> TXT specifying an appropriate SPF (there's sites online to help you

> generate one) so you can receive email.

>

> Please be aware though that email DKIM, webdisk, addon domains,

> subdomains, aliases, DNS, AutoSSL (for accounts on a server that's not

> Johnny) and numerous other features will NOT function in this

> configuration. For full functionality, you'll need to transfer the domain

> to a proper registrar and use our name servers.

>

> Also, please keep in mind that we do not support any account or domain

> that does not use our name servers, so we will be unable to provide support

> for your account if you choose to use it in this configuration.

>

> I'm not sure why CF says it's an uncommon requirement to require you use

> the host's name servers, it's actually the default configuration in cPanel,

> and a major security risk to allow otherwise (requiring the NS change is

> how we make you prove you own the domain).

>

>

> You may view the status of your ticket by visiting:

>

> https://www.helionet.org/index/index.php?showtopic@631

>

> Thank you,

> Heliohost support

> https://www.heliohost.org/

> https://www.helionet.org/

>

>

Posted

Since you have the queued message showing now (I saw a timeout earlier and figured you hadn't set it up), the issue is actually on our end. There's something wrong with Ricky at the moment that's causing that queued page...Apache hasn't restarted in 2 days. It's supposed to restart every 2 hours. Until it restarts, the domain won't finish setting up.

 

I'll pass this on to get that issue fixed, once that happens, you should be able to clear your cache and see your site.

Guest
This topic is now closed to further replies.
×
×
  • Create New...