13 replies to this topic

[logicPwn]

I signed up for CloudFlare and set it up and now my WordPress blog is down. I deactivated it in the DNS editor to bypass CF.

Thoughtful Coding « Logic Applied ElsewhereThoughtful Coding

[Roger]

This happened to CODECALL too last year when I flipped the site to CloudFlare.

[logicPwn]

Roger said:

This happened to CODECALL too last year when I flipped the site to CloudFlare.

How'd you solve it?

Edit: I think it has to do with the external script minify. If I go to http://tlokzz.info/blog/ then it shows it with no styles and not to mention it says no blogs available.

[Alexander]

My usual route of debugging:

1. Went to address, to confirm it was not only you experiencing the issue
2. Style sheets were not active, had opened source, pressed on one of their addresses
3. Had noticed Firefox could not find www.blog.tlokzz.info

Then it reminds me of what you had spoken prior:

Quote

I deactivated it in the DNS editor

Deactivated what?

Your domain likely points to a nameserver owned by CloudFlare, which is confirmed by querying:

;; QUESTION SECTION:
;www.blog.tlokzz.info. IN A
;; AUTHORITY SECTION:
tlokzz.info.     10800     IN     SOA elle.ns.cloudflare.com. dns.cloudflare.com. 2012021215 10000 2400 604800 3600

You may have to either enable CloudFlare's DNS control and add the subdomains "www." and "www.blog." to its DNS (pointing to your real server of course) for the blog to work, or go to your domain hosting panel and modify the nameserver back to your old one disabling CF. If this is already the case it may take some time for the changes to be reflected to the world.

Please feel free to clarify, I am a little rusty on how CloudFlare works, or what you have actually disabled.

Alexander.

[logicPwn]

In CloudFlare you have DNS settings which have all your redirects or w/e there called. blog points to the same IP as tlokzz.info does, so that should be correct. It took a while to happen when this change occured. So I am pretty sure it is something to do with the DNS. I'm glad you did those tests to show the DNS because I talked to my host provider JustHost.com and one of there techs say that PipeDNS (sister company that provides Domain names) interface from CPanel doesn't work. So I emailed them that I needed the DNS name servers changed. I thought that whole thing seemed bogus since in PipeDNS is has where you can change them and when I did it has an red x icon under our nameservers? Which is this scenario is good. W/e just one big clusterfuck and it's beginning to irritate me since I have been finally getting some good hits from the Chromium Updater program that I created. Bummer.

P.S. Auto-Save on the post saved my life :)

[Alexander]

You will have to use their DNS control panel to point www. and [noparse]www.blog.[/noparse] subdomains along with tlokzz.info. Currently, only your main domain is being pointed to CloudFlare, and is why nothing else works:

...
tlokzz.info    IN    A    199.27.134.42    300s    (00:05:00)
tlokzz.info    IN    A    173.245.60.118    300s    (00:05:00)
tlokzz.info    IN    MX    
...

i.e.

• Firefox queries cloudflare for[noparse] www.blog.site.com[/noparse]
  
• There is no A record for [noparse]"www.blog."[/noparse]
  
• Breaks connection

After 300 seconds or x hours or x days until everything is propagated to the world you should have access to your blog.

[logicPwn]

Hmm for some reason www. before my site has never worked perfectly. Maybe somethings fudged up on my host providers end. I am on an old cheap plan.

---------- Post added at 06:17 PM ---------- Previous post was at 05:58 PM ----------

Proof that my domain doesn't like www.

Portfolio | logicPwn
http://www.portfolio...info/index.html

try em out

That would be because my DNS for my site sucks right? **** cheap plans.

---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------

Since portfolio.tlokzz.info works and www.blog.tlokzz.info doesn't that means the WordPress script makes it use www correct? Maybe I can change some settings in WordPress to change the site address to tlokzz.info/blog/. To bad I can't access it. Frustrating.

[logicPwn]

Ran a traceroute on blog.tlokzz.info and confirmed its going through CF servers
Pingdom Tools

www.blog.tlokzz.info says Invalid Domain Name
Pingdom Tools

Home | logicPwn shows it's not using CF servers
Pingdom Tools

Must be the www in CF correct?

Edit: Ticked www to pass through CF and now it resolves to CF servers. This seems interesting though. MX lookup resolves to 2 a records to different IP addresses
Network Tools: DNS,IP,Email

[Alexander]

Have you passed the subdomain "www.blog" (not www. + blog. separately) to be allowed as you have with www. and portfolio? "www.blog" is a compound subdomain, and I have never seen it purposely used.

Your www.blog subdomain has this A record:

;www.blog.tlokzz.info.        IN    A

It is not pointing to any server at all and appears to be disabled at some end.

Quote

That would be because my DNS for my site sucks right? [...]

From what I gather, CF is your DNS provider. Your old DNS provider was also a domain reseller if you had purchased it from them, they can only control domain registration and what nameserver the domain should point to and you are not using their DNS any longer.

[logicPwn]

Well I am no? It's still managed through PipeDNS and then CF

I added a record www.blog.tlokzz.info to point to the same IP

Edit: Just removed CloudFlare, all the cache was to much, more for like a more popular site that has lot of traffic. I'm a developer and no one knows my site exists lol

Edited by logicPwn, 13 February 2012 - 02:24 AM.

[Alexander]

logicPwn said:

Well I am no? It's still managed through PipeDNS and then CF

logicPwn said:

JustHost.com and one of there techs say that PipeDNS (sister company that provides Domain names)

Your only link to any DNS provider is the authoritative nameserver (AN). Your DNS provider has requested that it be modified to point to CF's, and therefor you have had to go through your domain reseller/manager (PipeDNS, misleading name, not DNS!).

Your DNS provider is Cloudflare completely and is unrelated to PipeDNS other than it telling where CloudFlare's AN can be found for DNS, and would not benefit from delegating back to JustHost's DNS service. It would lose it's distributed DNS benefit and as well cause overhead penalty.

Quote

I added a record www.blog.tlokzz.info to point to the same IP

That address appears to be working for me. It would be interesting to understand why CF could not copy records over as it says it will do automatically, or what you have specifically done for it to not resolve. All subdomains are treated as separate addresses until the DNS simply points an A record to JustHost's hosting IP.

As per your question above on how CodeCall had fixed this issue, we had to remove the service - it had attempted to modify too much and ruined stability.
Side note: You should keep your CSS files on the same (sub)domain, less penalty to look up a subdomain if at all possible.

[logicPwn]

Ahh nice it's working now. Seems I have double my records one with www. and one without.