Page MenuHomePhabricator

non-wikimedia.org domain names for status page
Closed, ResolvedPublic

Description

We need at least one custom domain registered solely for the status page.

  • An external provider (Atlassian) is hosting the site, so per our own policy we can't use a subdomain of wikimedia.org
  • We don't want to use a subdomain of wikimedia.org anyway, because we want the status page to be totally dependent of our infrastructure (which includes DNS)
  • In order to use custom CSS/HTML/JS, Atlassian requires you to use a custom domain, rather than a subdomain of statuspage.io. We need custom CSS/HTML/JS both for styling, and also to do i18n/l18n.

I recommend we register both wikimediastatus.net and also wikipediastatus.net (a simple redirect to the former). I also think we should register .org and .com variants.

We'll also need simple static DNS hosting for both of those, although I expect that to be trivially provided by our registrar.

Event Timeline

About the process to buy domains at WMF:

Technically there is the Domains tag here in Phabricator but don't expect that to be monitored closely.

I would suggest to mail Chuck Roslof (croslof@) of legal to make sure they have it on their spreadsheets.

Then ask our contact at MarkMonitor Doneva.Daggett@markmonitor.com to please register it and make sure to tell them that we do NOT expect them to point it to Wikimedia NS as usual but to something different.

Though, I just saw that Doneva has moved on from MarkMonitor (https://www.linkedin.com/in/doneva-daggett-05960332) so we need to establish the new contact and see who responds.

@CDanis do you think that in the meanwhile we should put a link to the new status page in the existing places that comes first in search engine results like [1] and [2]? Or we consider this still "beta" until we fix the domain and procedures for human updates?

[1] https://status.wikimedia.org/
[2] https://meta.wikimedia.org/wiki/Wikimedia_servers#Status_and_monitoring

@CDanis do you think that in the meanwhile we should put a link to the new status page in the existing places that comes first in search engine results like [1] and [2]? Or we consider this still "beta" until we fix the domain and procedures for human updates?

[1] https://status.wikimedia.org/
[2] https://meta.wikimedia.org/wiki/Wikimedia_servers#Status_and_monitoring

Beta for now. I'll file a set of tasks that I think are blockers for a launch.

@mark @RobH Chuck Roslof from Legal has registered these domains, and has advised me that one of you two should be able to help me with access to Markmonitor to get them set up.

I didn't find a login in pwstore; if you can give me one that would be ideal.

Otherwise, can you please add the following record:

www.wikimediastatus.net CNAME nnqjzz7cd4tj.stspg-customer.com

And, assuming we have a URL redirection service from Markmonitor, can you please make all of the following redirect to www.wikimediastatus.net:

wikimediastatus.net
wikimediastatus.org
wikimediastatus.com
wikipediastatus.com
wikipediastatus.org
wikipediastatus.net

Please note this is the first I'm hearing of this, and I've been on vacation until today. (My phabricator calendar should have showed this when I was added in.)

There is not a shared login for this, as MarkMonitor handles all our domains, it is a per user login.

My login is expired, as it expires if not used within 30 days or so. I typically just emailed our rep Doni in the past. As she has moved on, I've emailed her old markmonitor email in hopes of a redirection reply.

@CDanis: What makes you think we have a redirection service? I don't recall ever getting this, or using any kind of redirection with MarkMonitor.

IRC Update:

Chatted with Chris about this in IRC, and CC'd him into the email thread with our MarkMonitor rep. We're working on this with the MM team.

@mark @RobH Chuck Roslof from Legal has registered these domains, and has advised me that one of you two should be able to help me with access to Markmonitor to get them set up.

I didn't find a login in pwstore; if you can give me one that would be ideal.

Otherwise, can you please add the following record:

www.wikimediastatus.net CNAME nnqjzz7cd4tj.stspg-customer.com

And, assuming we have a URL redirection service from Markmonitor, can you please make all of the following redirect to www.wikimediastatus.net:

wikimediastatus.net
wikimediastatus.org
wikimediastatus.com
wikipediastatus.com
wikipediastatus.org
wikipediastatus.net

Update:

MarkMonitor pointed wikimediastatus.net to their own nameservers, and also setup redirection for the other domains listed, and set the cname requested. None of these services by MarkMonitor result in more charges.

I think this is now resolved, but will let @CDanis review before closing.

Almost all set, just one last thing:

Just one last thing: can you please also set up a redirect at the root level of wikimediastatus.net ?

Since our status page hosting provider requires their record be a CNAME, that can only exist as a www. sub-record in that zone. And as is, http://wikimediastatus.net/ doesn't work as there is no A record at the root.

So if you could add an A record at the root of wikimediastatus.net, and have that serve an HTTP redirect to www.wikimediastatus.net, that would be great.

FWIW, the bare A record at wikimediastatus.net points to our own infrastructure (192.237.162.200, the same IP as status.wikimedia.org). So in case of an outage http://www.wikimediastatus.net would work but http://wikimediastatus.net would be down.

It's not quite within our own infrastructure -- that IP is also known as wikitech-static.wikimedia.org.
https://wikitech.wikimedia.org/wiki/Wikitech-static

We're not thrilled with this compromise but it was the best option available to us given a few constraints -- it turns out that Markmonitor won't do HTTP redirects except at a whole-DNS-zone level, and Atlassian requires a CNAME record (which can't go at zone apex).

CDanis changed the visibility from "Custom Policy" to "Public (No Login Required)".Apr 4 2022, 11:50 PM
CDanis changed the edit policy from "Custom Policy" to "All Users".