What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 127 Stack Exchange communities.

According to discussion in our chat, and downforeveryoneorjustme, http://rpg.stackexchange.com is down. I can still access it, so I think it's a DNS thing.

Update: Gaming seems down too, and a number of others mentioned in the comments

Update: Everything seems solidly back up. 2010-10-12 10:55 EST.

share|improve this question

closed as too localized by ChrisF, Tobias Kienzler, Robert Harvey, Robert Cartaino Oct 12 '10 at 16:30

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

    
English Language and Usage, too. I had just composed a comment there, and bam, it got eaten. –  ЯegDwight Oct 12 '10 at 14:11
    
Cooking is down too. –  jjnguy Oct 12 '10 at 14:11
    
And Unix, if any more examples are needed :). WA and AU both seem fine, and the trilogy –  Michael Mrozek Oct 12 '10 at 14:12
    
Android is also down –  Bryan Denny Oct 12 '10 at 14:13
    
Since it hasn't been mentioned yet, Webmasters is up. –  Rebecca Chernoff Oct 12 '10 at 14:15
2  
@rchern: it's down for me (and downforeveryoneorjustme). –  ЯegDwight Oct 12 '10 at 14:20
    
Gaming is up for me –  jmfsg Oct 12 '10 at 14:20
    
possible duplicate of http://meta.webapps.stackexchange.com/ is "Unknown Host"? –  ChrisF Oct 12 '10 at 14:20
3  
@ChrisF I would probably close in the other direction, since this is older and has a bunch of comments –  Michael Mrozek Oct 12 '10 at 14:21
    
@Michael - I normally check, but didn't in this case. The other one's been closed now though. –  ChrisF Oct 12 '10 at 14:26
    
math.stackexchange.com is up while meta.math.stackexchange.com is down o_O –  KennyTM Oct 12 '10 at 14:26
1  
@KennyTM Both down for me. I imagine *.stackexchange.com is down depending on who does the query –  Michael Mrozek Oct 12 '10 at 14:29
3  
NOT PROGRAMMING!! Waah! –  Mark C Oct 12 '10 at 14:30
1  
Whoops, I meant "Programmers", but I think the others figured it out. –  Mark C Oct 12 '10 at 14:39
3  
All sites are up again for me! –  ЯegDwight Oct 12 '10 at 14:44
show 8 more comments

4 Answers

up vote 8 down vote accepted

This was a result of my ignorance of how wildcard mappings work. I had converted our wildcard mapping but left some sub domains around. If a subdomain still exists, at least with our DNS provider's implementation, it will not resolve.

In Summary:

*.foo.com does not work for arf.foo.com even if arf.foo.com doesn't exist if baz.arf.foo.com does.

As far as the kyle.stackoverflow.com entry, I am will have to contact our provider to find out why that is there.

share|improve this answer
4  
+1. It is extremely refreshing to have an admin admit they made a mistake. I wish more admin's would learn that trait. –  Diago Oct 12 '10 at 16:14
add comment

% dig cstheory.stackexchange.com.

stackexchange.com. 59 IN SOA ns1.p19.dynect.net. kyle.stackoverflow.com. 53 3600 600 604800 60

Each of the four servers listed for stackexchange.com has the same information. That "53" looks like someone made a typo and replaced the zone serial number with the port number for DNS, and perhaps the rest of the zone file is borked also. I suggest the StackExchange folks get in touch with the person who last edited the stackexchange.com zone file. I will email kyle@stackoverflow.com too.

share|improve this answer
    
Or the serial number is 53 by accident, but that wouldn't conform to guidelines to have something like: 2010101201 (year/month/day/edit) –  Tom Wijsman Oct 12 '10 at 14:43
    
It seems highly unlikely that stackexchange.com, which hosts dozens of sites that are in the Area 51 process, would only have been edited 52 times. –  András Salamon Oct 12 '10 at 14:49
    
Looks fixed now, the 60 second time-to-live will cause this to hang around for a little while but it should be back to normal shortly. –  András Salamon Oct 12 '10 at 14:51
add comment

All sites that have alternate URLs are reachable through those URLS. No site can be reached through its .stackexchange.com URL right now. Something's up with the StackExchange DNS server. What, I do not know.

share|improve this answer
    
Chinese hackers, that's what. –  Mark C Oct 12 '10 at 14:31
    
except for meta.stackexchange.com and area51.stackexchange.com and non-existent ones like somewhere.stackexchange.com –  Tobias Kienzler Oct 12 '10 at 14:32
add comment

I guess the DNS itself would be up as the chats are still available, but the other entries are acting weird.

The sites itself are up too, as adjusting the HOSTS file helps:

69.59.196.211 gaming.stackexchange.com
69.59.196.211 meta.gaming.stackexchange.com
share|improve this answer
    
that's twice stackoverflow.com for me - you mention the same IP twice! –  Tobias Kienzler Oct 12 '10 at 14:31
2  
That's how HOSTS files work... ;-) –  Tom Wijsman Oct 12 '10 at 14:32
add comment

Not the answer you're looking for? Browse other questions tagged .