Page MenuHomeMiraheze

Review all custom domains with unusual rDNS entries
Open, Stalled, NormalPublic

Description

By checking the rDNS entries for resolved IP addresses for custom domains, we can determine whether they directly point to Miraheze cache proxies or not. For example, some wikis use Cloudflare's proxy options, despite telling them in the manual they shouldn't do that.

An automated check was introduced in this commit. Per IRC asking RhinosF1 to review all warnings and criticals:

For each wiki, the actionable (after asking the user with the ability to change DNS records) can be:

  1. Switch the record to CNAME mw-lb.miraheze.org, with the proxy option disabled, or
  2. Set the DNS nameservers to our auth DNS servers, or
  3. If the domain does not longer (indirectly) point to Miraheze: remove the custom domain.

Event Timeline

Southparkfan triaged this task as Normal priority.
Southparkfan updated the task description. (Show Details)
Southparkfan updated the task description. (Show Details)

Thanks @Southparkfan,

As discussed on IRC, we'll send 2 notifications within the next 14 days. No response = CD revoked.

I plan to send both on wiki message and email.

RhinosF1 added a comment.EditedWed, Jul 29, 21:34

Wikis where they don't serve a Miraheze wiki will be removed in the morning. For ones that do, as above crats will have 14 days to make the change.

RhinosF1 updated the task description. (Show Details)Thu, Jul 30, 08:23

All not serving Miraheze have been pulled and unset, I will alert crats for them wikis shortly.

RhinosF1 updated the task description. (Show Details)Thu, Jul 30, 08:57
RhinosF1 updated the task description. (Show Details)Thu, Jul 30, 09:38
RhinosF1 updated the task description. (Show Details)Thu, Jul 30, 09:56
RhinosF1 changed the task status from Open to Stalled.Thu, Jul 30, 10:01
RhinosF1 removed RhinosF1 as the assignee of this task.

Stalling for 7 days, then will send 2nd notification.

7 days after that, we'll drop any left.

RhinosF1 updated the task description. (Show Details)Fri, Jul 31, 06:53