Help us figure out DNS problems... part 2
Part 1
Our CDN has been disabled for 48 hours now because of DNS lookup failures, and our site is depressingly slow. There are other side effects too, such as PDF reports breaking (although we did just fix that), widgets breaking, etc. We need to get this resolved ASAP but need your help to do it.
As of now, the CDN has been re-enabled. I hate to do this but yes I am intentionally breaking the site again for the small percentage of you who have been affected. This is so as soon as it breaks, you can run the following command to trace the path of the entire DNS lookup so we can figure out exactly whose side is failing (DNS Made Easy, or Cloudflare). Neither of them can replicate the issue or find any problems on their end, so ultimately we need your help to figure out where it's breaking.
So, if anything looks broken to you, immediately copy/paste the following command into a unix shell (Mac or Linux only, sorry Windows users) and hit enter:
dig cdn.staticstuff.net | sed -nr '/^;; ANSWER/,/^$/ { s/^([^t]*.)t.*/dig +trace 1 ANY/p}'|uniq|sh
It will take about 5 or 10 seconds to run. Then, copy/paste the entire output into a comment here. It will be about 100 rows of text.
We hope to get this resolved ASAP but since no one on our side of things can replicate the issue, we absolutely need your help here.
8 comments | Aug 01 2012 8:36pm
Our CDN has been disabled for 48 hours now because of DNS lookup failures, and our site is depressingly slow. There are other side effects too, such as PDF reports breaking (although we did just fix that), widgets breaking, etc. We need to get this resolved ASAP but need your help to do it.
As of now, the CDN has been re-enabled. I hate to do this but yes I am intentionally breaking the site again for the small percentage of you who have been affected. This is so as soon as it breaks, you can run the following command to trace the path of the entire DNS lookup so we can figure out exactly whose side is failing (DNS Made Easy, or Cloudflare). Neither of them can replicate the issue or find any problems on their end, so ultimately we need your help to figure out where it's breaking.
So, if anything looks broken to you, immediately copy/paste the following command into a unix shell (Mac or Linux only, sorry Windows users) and hit enter:
dig cdn.staticstuff.net | sed -nr '/^;; ANSWER/,/^$/ { s/^([^t]*.)t.*/dig +trace 1 ANY/p}'|uniq|sh
It will take about 5 or 10 seconds to run. Then, copy/paste the entire output into a comment here. It will be about 100 rows of text.
We hope to get this resolved ASAP but since no one on our side of things can replicate the issue, we absolutely need your help here.
8 comments | Aug 01 2012 8:36pm
Recent Comments
Cool beans. We've been using local search on one of our sites for a while and it's ... Shaun Peet, May 16 2013 Not yet. But we will support that. Sean (Clicky), Apr 22 2013 I'll try again... "My search looks like this: http://www.rdo.co.uk/search/ ... Matt, Apr 22 2013 Yeah that's definitely an option. It would probably be a clicky_custom property though ... Sean (Clicky), Apr 19 2013 Yes the utm_custom tracking will be great. You say only apply to certain tags like ... Andy, Apr 19 2013 > Any way to get this to work when there is no explicit parameter in the URL? My ... Jean-Paull, Apr 18 2013 Here is my search string as it appears in browser; index.php?src=search&searc ... Chris Theisen, Apr 18 2013 Ah, so that is why Clicky stopped logging my dynamic sales goals a while ago... Ivan Arnaudov, Apr 18 2013 Nice feature, but.... we dont use search parameters. ( our sites have ajax searches, ... Gerwin, Apr 17 2013 Thanks for the response. I'll wait and check it tomorrow! Darin, Apr 17 2013