575035 - create blog.mozilla.org redirect to blog.mozilla.com?

Status: RESOLVED WONTFIX

(mozilla.org Graveyard :: Server Operations, task)

Description

[Jeremy Baron]

blog.mozilla.org was linked from tonight's mozilla.announce post. (and I received via the corresponding mailman list)

It seems to not exist (I'm getting NXDOMAIN when hitting auth DNS) atm but blog.mozilla.com does exist.

maybe blog.mozilla.org should redirect to blog.mozilla.com?

$ for i in www blog; do dig $i.mozilla.org @ns1.mozilla.org | fgrep -e 'status: ' -e ";$i"; done
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: xxxxx
;www.mozilla.org.               IN      A
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: xxxxx
;blog.mozilla.org.              IN      A

Comment 1

[Reed Loden [:reed]]

Considering only MoCo employees can get blogs on blog.mozilla.com, it would not make sense for blog.mozilla.org (MoFo) to redirect to blog.mozilla.com (MoCo).

Comment 2

[Justin Wood (:Callek)]

And why not for a redirect, the distinction between foo.mozilla.org and foo.mozilla.com are few and far between as far as actual USER and HUMAN understanding.

There are a few exceptions, but if blog.m.o is guaranteed never to exist (at least forseeable future) I preclude that a redirect makes sense to avoid DNS lookup fails, and frustration.

Even the release announcement writers can get mixed up due to this distinction.

Comment 3

[Shyam Mani [:fox2mike]]

Don't really think this redirect is warranted.

Comment 4

[David Boswell]

I agree that having some sites on mozilla.org and some sites on mozilla.com (not to mention mozillamessaging.com) is confusing and exposes a lot of information about our legal organizations that is irrelevant to most people.

Instead of fixing this site by site though, we opened a governance bug to set a general policy about domain names at bug 495800.  Please feel free to add thoughts or suggestions there.