Going to meta.stackexchange.com will give you a 503 Service Unavailable error. Since this meta is the de facto meta for the entire network, wouldn't it make since to redirect it here?

If not, I'm curious about the reasons for not doing so.

  • 1
    I tried and meta.stackexchange.com redirects to MSO. meta.stackexhange.com, however, leads to some uninteresting list of spam links. Not sure if it got fixed in the process or it was a typo from the beginning. – Dennis Jul 13 '12 at 4:05
  • @Dennis Interesting. The "meta.stackexchange.com" link in your comment shows me a "503 Service Unavailable" error, like RLH reported. – Jeremy Banks Jul 13 '12 at 4:09
  • @JeremyBanks: Nevermind. Chrome had already cached the 301. I tried in IE and got the error. – Dennis Jul 13 '12 at 4:12
  • Aaaand it's fixed! – Kalamane Jul 13 '12 at 4:18

No, it shouldn't. The problem was that there was two definitions in the zone file - i've fixed it so that meta.stackexchange.com now only has one DNS entry.

So this won't affect everyone equally - depends on which response you get back first. This should clear up in about half an hour (unless you have a crappy DNS provider who ignores our TTLs)

C:\Users\gbeech>nslookup meta.stackexchange.com
Server:  ny-dc01.ds.stackexchange.com

Non-authoritative answer:
Name:    meta.stackexchange.com

This just cropped up because Fog Creek finally shut down those load balancers that were forwarding the traffic to us.

  • Rebecca is involved? It's a conspiracy!!! – animuson Jul 13 '12 at 4:23
  • @animuson nah she just didn't like my bad spelling – Zypher Jul 13 '12 at 4:24
  • If that were true, she would have fixed the word "do" in the last sentence there. :o – animuson Jul 13 '12 at 4:25
  • @animuson what word do? – Zypher Jul 13 '12 at 4:28
  • @animuson gotta keep you guessing. – Rebecca Chernoff Jul 13 '12 at 4:33

You must log in to answer this question.

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