Long time no see! Working on the OG wiki, feels good so far.
How is the restroration progress going 💀

I'll close this as it's not that important for me right now, although I think it would be a good idea to set up cookie blocking across subdomains, so that custom subdomain functionality is available to users with domains.

Let's hope we found them or have me a backup if Alzheimer haven't come to this part yet...

And man, the wiki is deleted 2 days before the closest .tar.gz backup...

In T10362#209652, @Reception123 wrote:

You don't happen to have a backup of the wiki do you? That would make things much easier/faster.

You don't happen to have a backup of the wiki do you? That would make things much easier/faster.

In T10362#209608, @Reception123 wrote:

Accidental close.

Accidental close.

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.)

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.

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

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.

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/

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.

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:

But unfortunally, as mentioned by Agent_Isai at Steward' noticeboard, I have to ask for a restore for lhmnfanon

I hate how much are CNAME flattering...
But yeah, let's do the fanon one...

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

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.

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)

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.

I think you put the wrong IP in. Should be 95.217.135.175 not 95.271.135.175.

should be done

If you just want to turn fankit.lophocmatngu.wiki into a redirect, use GitHub Pages.

@Reception123 Yes, please, as OrangeStar explained.

Regarding fankit.lophocmatngu.wiki, we do not redirect Miraheze subdomains to any external websites for security reasons.

And, you know what I mean, right? I can't just hang another .wiki subdomain and create another landing page that does not necessary.

How willing? I mean, I'm just wondering if they are capatible setting up URL redirect, as it's still, an DNS based settings... 🤔

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.

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.

How about setting up fanon.lophocmatngu.wiki as a CNAME to mw-lb.miraheze.org and setting the rest of the domains yourself on your DNS server instead of pointing the domain to Miraheze's DNS? I don't know how willing SRE will be to set those fankit and nguyet subdomains.

DKIM should usually be unique i guess

Confirmed.

Holding until the domain is successfully applied.

This is now done. It may take a little bit to take effect though.

Now done.

https://github.com/miraheze/dns/pull/282

No reason to wait several days. Anyone can make a PR in a few minutes for this.

I can do it within the next 30 minutes if you want also.

I can do this task in the next several days, if that's okay?

I can wait, it’s Low priority after all. ;-)

You should be able to use the html tag method via WikiSEO if you don't want to wait but we'll be able to do this.

Thanks for the request, we'll get on with it.

https://github.com/miraheze/dns/pull/261/files

Thank you!

done

Left the user a talk page message. They don't have an email set, so can't email them.

Thanking you for fixing this.

ns2 is ready to be deployed, domain registrar access from @Void and then 1&1 access from @Paladox before this can be deployed into production (both).

Done!

Unfortunately I don't know enough about it, I'm just passing on the instructions from Zoho. Could someone do it?

This is blocked on T8545.

No problem, someone will add them later today or you can edit the file at https://github.com/miraheze/dns/blob/master/zones/wikicryptos.org

Thanks a lot!

Done, should deploy within 30 minutes!

Transferred over to the Miraheze account and renewed. DNS settings look appropriate, though let me know if that is not the case. I'll be opening a new task shortly to discuss registrar access and details, as we should definitely replace SPF's details that is currently being used as the contact.

Not sure when labster and I will be in the same place at the same time. If I'm not around, it might be best to have him reach out directly to me (either via email or whatever else he prefers) so we can coordinate somehow.

Per the IRC discussion in -ops the domain will be transferred and paid for by SRE. Assigning to Void since they are the one with registrar access.

No miraheze.wiki = no status / phab etc

Resolved.

Both are maintained paths for internal purposes.