> It appears the nameservers for Stack Exchange are returning SERVFAIL for all queries, meaning most users are unable to access any Stack Exchange site, or will shortly lose access once their local DNS caches expire.
Answer as to the direct cause (posted to that question):
"We recently relocated our NY datacenter, and therefore all the IPs in NY changed.
We didn't update to the new IP for the master DNS server (in both the named.conf and the zone files), and therefore all of our slaves hit our expiry time (one week). This is fixed now, so things should start coming back up."
When Stack Overflow went down tonight my productivity dropped precipitously. It reminds me of how grateful I am of the team at Stack Exchange. They built one hell of a resource.
This evening realized how dependent I am on SO. Trying to figure out how to dynamically set parameters for a CSS animation (turns out it's harder than it sounds) and the only useful answers I can find are on SO. Also very glad to have Google's cached versions.
23 comments
[ 2.7 ms ] story [ 81.3 ms ] threadServer: google-public-dns-a.google.com Address: 8.8.8.8
* google-public-dns-a.google.com can't find stackoverflow.com: Server failed
Pretty bad...
stackoverflow.com - DOWN
serverfault.com - UP
cdn.sstatic.net - DOWN
Purely a DNS issue
e.g http://www.downforeveryoneorjustme.com/stackoverflow.com
> It appears the nameservers for Stack Exchange are returning SERVFAIL for all queries, meaning most users are unable to access any Stack Exchange site, or will shortly lose access once their local DNS caches expire.
"We recently relocated our NY datacenter, and therefore all the IPs in NY changed.
We didn't update to the new IP for the master DNS server (in both the named.conf and the zone files), and therefore all of our slaves hit our expiry time (one week). This is fixed now, so things should start coming back up."