Page MenuHomePhabricator

wikimedia.community domain name is not resolving an mx record
Closed, ResolvedPublic

Description

wikimedia.community domain name doesn't show an mx record therefor OTRS queue wmtr@wikimedia.community is not receiving mails.

Domain Type Class TTL Answer
wikimedia.community. NS IN 86400 ns0.wikimedia.org.
wikimedia.community. NS IN 86400 ns1.wikimedia.org.
wikimedia.community. NS IN 86400 ns2.wikimedia.org.
ns0.wikimedia.org. A IN 86400 208.80.154.238
ns1.wikimedia.org. A IN 86400 208.80.153.231
ns2.wikimedia.org. A IN 86400 91.198.174.239

Server Response Time:
Looking up at ns0.wikimedia.org. Reports 0 MX record(s). 119 ms.
Looking up at ns1.wikimedia.org. Reports 0 MX record(s). 148 ms.
Looking up at ns2.wikimedia.org. Reports 0 MX record(s). 33 ms.

Event Timeline

Reedy added a subscriber: Reedy.

Did this ever work? Or did someone just start using the email and expect it to work?

It's been working since 2016. I've just checked the queue and latest received email is dated 08/01/2019.

ema triaged this task as Medium priority.Dec 20 2019, 12:33 PM
ema moved this task from Triage to DNS Names on the Traffic board.

Hi All! Just wanted to drop a line to share that this is the address shared as the main communication email of the group in social media and other channels; so we'd like it work. Would it be possible to help on this? When we could expect it to get it work? Thank you.

Could anybody please explain why such an easy task does takes so long to get resolved? What can be done to expedite?

Could anybody please explain why such an easy task does takes so long to get resolved? What can be done to expedite?

Probably in part the time of year, holidays etc. I don’t know if SRE are likely to pick this up before the new year, to avoid unnecessary deploys in the break

It does seem like it taking 3+ months to notice it was broken is slightly odd... So why the urgency to get it fixed? ;)

Re-adding an MX record is not rocket science, this should be possible also at this time of the year, and not noticing missing e-mails if a different thing than actively ignoring a broken setup. IMHO.

Re-adding an MX record is not rocket science, this should be possible also at this time of the year, and not noticing missing e-mails if a different thing than actively ignoring a broken setup. IMHO.

It might not be, But as mentioned, Many of the Ops team such as SRE whose responsibility this fall under have low coverage due to the holiday season, Which is why there is a deployment freeze on at the moment.

Could anybody please explain why such an easy task does takes so long to get resolved? What can be done to expedite?

Yes: See https://www.mediawiki.org/wiki/Bug_management/Development_prioritization . "Rocket science" comments don't help. Patches do.

A formal deployment freeze sounds reasonable. Can you please advise for which day the change can be scheduled, so we can decide if an expensive interim solution is required, i.e. temporarily moving the whole stuff to a different e-mail address?

Did this ever work? Or did someone just start using the email and expect it to work?

It was purchased for OTRS by the looks T76277: Redirect wikimedia.community to wikimedia.org

Change 561587 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[operations/dns@master] Provide MX and SPF records for wikimedia.community

https://gerrit.wikimedia.org/r/561587

Change 561587 merged by Vgutierrez:
[operations/dns@master] Provide MX and SPF records for wikimedia.community

https://gerrit.wikimedia.org/r/561587

Vgutierrez claimed this task.
$ host -t mx wikimedia.community
wikimedia.community mail is handled by 10 mx1001.wikimedia.org.
wikimedia.community mail is handled by 50 mx2001.wikimedia.org.