I see that currently your wiki is being hosted at comprehensibleinputwiki.org so I'm not sure how this would be possible unless you changed to something like wiki.comprehensibleinputwiki.org. Or maybe I'm not understanding what you want to do exactly.

They want you to add a wildcard record: *.comprehensibleinputwiki.org IN A 95.271.135.175. It is technically possible without needing to move the wiki.

@Reception123 Yes, please, as OrangeStar explained.

Also, I don't have much experience, but I'm not sure the format in the DNS file is correct. I think somewhere there needs to be *.comprehensibleinputwiki.org.

Or maybe * A 95.217.135.175. I think @ is for root.

I've talked to John about this now and he's mentioned that there are security concerns with the change altogether as any website could access top level domain cookies if we don't host restrict them. In that case, my original suggestion stands (changing to wiki.comprehensibleinputwiki.org)

Oh ok, I prefer to have the wiki on the top level domain, so I'll just host the other part of the website on a different domain. Unless the security concern is related to it being *all* subdomains, in which case only pointing to one subdomain would work for me. Or if you know of another way to point the top level domain to MH but the subdomains to another server, that'd be great. If not, this can be closed.

Another option would be to only add a CNAME record and point it to "mw-lb.miraheze.org" and no longer point the NS to us

Do you know if Miraheze could do a root domain pointed with CNAME? I know my registrar has the ability to do it, but the MH Meta page only mentions subdomains:

Pointing a subdomain to Miraheze? Add a CNAME record on the subdomain you want (e.g. "wiki."), and point it to "mw-lb.miraheze.org";

CNAME on root domains is technically illegal according to the standards, as, if there's a CNAME, no other records other than DNSSEC-related records are allowed. There's ANAME for when you want to ignore the standards and still do this anyway, but I don't recommend using that.

Are you sure it's still against standards? The registrar has a slightly different name for it, CNAME flattening, and Cloudflare has a post about it being allowed: https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/

Yes, it is still against the RFCs as of today. Cloudflare doesn't return CNAMEs on root domains, it just resolves the CNAME on the authoritative nameserver and then return the A/AAAA record(s) instead of the CNAME, which technically complies with the spec as the recursive resolver never sees the CNAME at the root itself.

But CNAME flattening as Cloudflare does wouldn't work for this?

Why not? Is the same thing the recursive resolver would do, just done on the authoritative nameserver instead. I think it would work, but I don't think this solves the concerns with the cookies raised by John and Reception123.

Oh ok, well if it would be an issue, it's not a big deal as I can use my other domain. But maybe there's a way MH could block cookies from being seen by such subdomains. (I don't know much about how cookies work.)