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:
- not serving Miraheze
- https://espiri.wiki - notification sent
- https://hentailolicon.org- notification sent
- https://wiki.glaucuslinux.org - not attached to a wiki? - no phab task found
- https://wikis.kubixgames.com- notification sent
- https://pcgamingwiki.elijahpepe.com- notification sent
- https://wiki.animalrebellion.cz- notification sent
- https://wiki.bonziworldrevived.tk- notification sent
- serving Miraheze
- https://wiki.bydorn.de - notification 1 sent
- https://wiki.valkyrienskies.org - notification 1 sent
- https://wiki.iufs.jp - notification 1 sent
- https://wiki.titan.land - notification 1 sent
For each wiki, the actionable (after asking the user with the ability to change DNS records) can be:
- Switch the record to CNAME mw-lb.miraheze.org, with the proxy option disabled, or
- Set the DNS nameservers to our auth DNS servers, or
- If the domain does not longer (indirectly) point to Miraheze: remove the custom domain.