At roughly 02:05 EST, A report was received that the DoujinStyle website had gone offline. Response as to investigate was immediate and no fault was detected on EidolonHost's network, investigation continued.
Between 02:12 and 02:15 a discrepancy in DNS was noted by myself and Keiro Dreamwalker, that discrepancy permitted my access to the site as I utilize ns.digibase.ca as a DNS resolver which still had the old records from prior to CloudFlare deployment. Below is a transcript of records:
;; ANSWER SECTION: doujinstyle.com. 14400 IN A 220.127.116.11 ;; AUTHORITY SECTION: doujinstyle.com. 120 IN NS ns3.eidolonhost.com. doujinstyle.com. 120 IN NS ns1.eidolonhost.com. doujinstyle.com. 120 IN NS ns4.eidolonhost.com. doujinstyle.com. 120 IN NS ns2.eidolonhost.com.
commonly available record (obtained using Level3/gtei public DNS resolver: 18.104.22.168)
;; ANSWER SECTION: doujinstyle.com. 289 IN A 22.214.171.124 doujinstyle.com. 289 IN A 126.96.36.199 ;; AUTHORITY SECTION: doujinstyle.com. 43200 IN NS hugh.ns.cloudflare.com. doujinstyle.com. 43200 IN NS gina.ns.cloudflare.com
At 02:18, I performed tests against the commonly available "A" (IP address) records, executing HTTP Requests against them as if they directly hosted the DoujinStyle.com website, below is a transcript of those activites, I chose the HTML "title" element to base success off of:
$ wget --header='Host:doujinstyle.com' http://188.8.131.52 -O - |grep "<title>" <title>DoujinStyle.com - Doujin Soft, Doujin Music and Touhou</title>... Succeeded.
$ wget --header='Host:doujinstyle.com' http://184.108.40.206 -O - |grep "<title>" --2011-11-20 02:19:51-- http://220.127.116.11/ Connecting to 18.104.22.168:80... failed: Connection timed out.... Failed.
At 02:20 it had been determined that Cloudflare was experiencing issues on their network.
At 02:24 I investigated at Cloudflare's website: https://www.cloudflare.com/ and brought up their status page: https://www.cloudfla...m/system-status . It was determined that one or more of their nodes was encountering issues with attacks. Attacks were not directed toward DoujinStyle.com.
It was determined that CloudFlare introduces a point of failure and was further determined that its usage could compromise DoujinStyle.com's public uptime and stability as an attack against one or more sites utilizing Cloudflare can render a cloudflare node inoperative and thus take other sites offline including DoujinStyle.com.
At 02:34 Holy proceeded to switch DNS services from utilizing Cloudflare back to the ns1-4.eidolonhost.com DNS servers (of which ns2.eidolonhost.com is an alias to ns.digibase.ca), Propegation is pending.
At 3:24 I proceeded to perform testing against public DNS servers for propegation of the change:
Level3/gtei: 80% resolving correctly.
Google Public DNS: 0%