CloudFlare + cPanel Addon on VPS

[Geoff]

Im having issues with all my domains when enabling cloudflare through the addon ive installed in cPanel. Everything *appears* to be working, until you actually try to visit the website.

The weird thing is... I cant access it, and many others cant access it as well... but some people can! It seems to be about 50/50. Got on IRC and some people have no problems, but some people do. But its saying the domain isnt configured to serve pages. And its not random. Its not like some people can access it some of the time, its more like whoever can access it, can access it consistently. But those who cant, cant consistently. Oh and its just www. subdomain that isnt working. the non pointed url works fine (although for consistancy ive htaccess'd it to point to www because cloudflare only works on cnames)

Oh and www pointers work fine when cloudflare is disabled. So I dunno whats going on

Here is the error im getting:


Here is my zone file.



This is what CloudFlare had to say on the matter

On the other hand, it seems like www.travellingoz.ca seems to be working:

curl -A Mozilla/5.0 -I www.travellingoz.ca
HTTP/1.1 200 OK
Server: cloudflare-nginx
Date: Wed, 26 Dec 2012 22:28:45 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
X-Powered-By: PHP/5.3.19
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Cache-Control: no-cache
Pragma: no-cache
Set-Cookie: f058399d514e12d665a79454d54b2191=063243cba38485b86 3a1a04620c86119; path=/
Set-Cookie: __cfduid=d06799338dccd9286574a7cb4f798446a13565609 25; expires=Mon, 23-Dec-2019 23:50:00 GMT; path=/; domain=.travellingoz.ca
CF-RAY: 271b2d674d6012a----------------------------------------------

So i dont know if its a CloudFlare issue, a server/cpanel issue, or a user/browsing issue? Any help would be greatly appreciated.

Regards.

[Geoff]

This is the latest from CloudFlare

The cPanel plugin uses cPanel's own API to make modifications to DNS. The provisioning part of the for CloudFlare is likely working. (That is the Host API part.)
From what it sounds like, however is that the DNS changes aren't being made. If this is the case, then you may want to look into why that is in your cPanel documentation.

But to the best of my knowledge/experience, everything looks okay.

[Kelly]

Hmmm, according to this blog post that error should go away after ten minutes or so:

http://blog.cloudflare.com/cloudflar...ps-after-activ

[Geoff]

Ya, but my problem hasnt gone away. So it says i should contact them. Which i have. And support has been less than helpful. Well theyve been helpful in the sense "Its not our problem, its yours (probably dns misconfiguration), but heres some suggestions"

but ya. The sites work fine when cloudflare is disabled. But when its enabled a bunch of people have no problems accessing the domains, but I and a bunch others get a cloudflare error. So its working 50/50. 3 days later and theres no resolution in sight. In fact they are still "dig"ing my dns and telling me things look wonky, but they arent. I just have dizinc and custom name servers setup on the server. Both of which have been working fine for years. but they define this as "peculiar". i define it as redundancy? either way both point to the same server.

[Geoff]

Status: Resolved!

Finally after they did some tests on their end, they informed me that my name servers were refusing connections from some of their datacenters. It was not my server but the name servers specifically, so i started to examine named.conf a little closely, and the only section to deny a host was in the bogon section. Apparently i had some sort of legacy bogon list that included previously unallocated IP's that have since been allocated when IPv4 addressing was maxed out. CloudFlare received some of these IP's

So after i cleaned up the named.conf bogon list, everything was functioning.

I wonder though is this bogon list part of a default named.conf config? or cpanel? or surpasshosting? i knew you could exclude hosts in named.conf but i wasnt aware it included a default list...

But glad to have the problem resolved. Spent close to 3 days trying to figure this out lol