[Answered] Cloudflare & Heliohost

[liamraystanley]

Hi I've been trying to set up a domain "www.brocrafting.net" using the cloudflare nameservers, and an A record pointed towards stevies IP address. Obviously with no avail just yet. :3

the www.brocrafting nameservers are currently pointed towards the two cloudflare.com nameservers

 

The root domain of www.brocrafting.net is pointing to:

;; CNAME Records
direct.brocrafting.net.	300	IN	CNAME	brocrafting.net.

;; A Records (IPv4 addresses)
www.brocrafting.net.	300	IN	A	216.218.192.170
brocrafting.net.	300	IN	A	216.218.192.170
ftp.brocrafting.net.	300	IN	A	216.218.192.170
*.brocrafting.net.	300	IN	A	216.218.192.170

 

(as you can see, the TTL is very low so the propagation is instant over at CloudFlare.)

Here is a dig
; <<>> DiG 9.8.3-P4 <<>> www.brocrafting.net

;; QUESTION SECTION:
;www.brocrafting.net.		   IN	  A

;; ANSWER SECTION:
www.brocrafting.net.	300	 IN	  A	   216.218.192.170

 

 

yet I still receive the "It seems your NameServers aren't pointed to blahblahblah"

Any questions or solutions to this issue?

[Shinryuu]

Here are my settings for CloudFlare:

And on dot.tk:

 

Didn't take long to finish setting up, 10-15 minutes maybe.

[liamraystanley]

This means that the right nameservers were used to point to CF.

 

 

and this...

Means it is pointed towards the IP.

 

"Error from park wrapper: Using nameservers with the following IPs: 173.245.59.116,173.245.58.134 Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameserver."I

 

So, I guess I'll wait a little longer, to see if any propagation is the cause. (but when I head over to brocrafting.net it leads to the "Account creation" stuff, meaning it is in fact the right IP now.

[Krydos]

I've found the easiest way to set up cloudflare is the following.

1. Set your domain's nameservers to ns1.heliohost.org and ns2.heliohost.org
   
2. Park, or addon your domain through cPanel.
   
3. Wait 24 hours and make sure your domain is working as expected.
   
4. Log into cloudflare's website, and type in your domain.
   
5. Cloudflare will copy all the existing, proven to work settings and instruct you to change your nameservers to something like olga.cloudflare.com and cleetus.cloudflare.com.
   
6. Log into your domain registrar's website and make the changes.
   
7. Wait 15 minutes to 48 hours for your DNS changes to go through, and cloudflare will alert you when everything is good to go.
   

Obviously, there are shortcuts for everything, but this process leaves the least room for error and pretty much guarantees you a functional set up.

[liamraystanley]

I've found the easiest way to set up cloudflare is the following.

1. Set your domain's nameservers to ns1.heliohost.org and ns2.heliohost.org
2. Park, or addon your domain through cPanel.
3. Wait 24 hours and make sure your domain is working as expected.
4. Log into cloudflare's website, and type in your domain.
5. Cloudflare will copy all the existing, proven to work settings and instruct you to change your nameservers to something like olga.cloudflare.com and cleetus.cloudflare.com.
6. Log into your domain registrar's website and make the changes.
7. Wait 15 minutes to 48 hours for your DNS changes to go through, and cloudflare will alert you when everything is good to go.

Obviously, there are shortcuts for everything, but this process leaves the least room for error and pretty much guarantees you a functional set up.

 

 

Shinryuu got me to this point, but it seems now that my email won't work.

 

(and yes, I am now doing it with liamstanley.net)

 

Also I recommend adding an A record * pointed to the IP of your server. (so that anything not listed on CloudFlare is auto forwarded to the server)