will resume debugging in the AM

Detected this fault because my Norton VPN was on. I have raised case #83340332 with them and are currently liasing with support.

I guess this is finished then.

There's no point really. We have mirabeta.org now and there's no point in spending money on betaheze.

In T11280#226737, @Routhwick wrote:

At this writing, though, typing in betaheze.org leads to a blank-slate homepage parker courtesy of IONOS; that much I noted at the Community noticeboard last month (along with the current status of @MirahezeStatus on X/Twitter). Did the departed volunteers abandon it back in June as well, or did someone forget to pay the bills?

At this writing, though, typing in betaheze.org leads to a blank-slate homepage parker courtesy of IONOS; that much I noted at the Community noticeboard last month (along with the current status of @MirahezeStatus on X/Twitter). Did the departed volunteers abandon it back in June as well, or did someone forget to pay the bills?

17:42 <Voidwalker> Looks like cron crashed leading to duplicate services being started repeatedly

rebooted and currently being investigated by @Void CPU use was at 100% and server was inaccessible.

**This is the truth Miraheze is burning like a house and the suppoesed firefighters are sitting relaxing having a coffee instead of helping

Looks like someone has done this.

We can go ahead and drop .ml and .ga from the DNS repo, as I’m dropping the registration, I’m only retaining the .tk and .gq

freenom lost .ga awhile ago, and seems like they may have lost .ml just recently.

The wiki is no longer accessible at the given URL due to this issue.

Alhamdulillah, it's working.
thank you very much.

Please try now. (in ~10 mins)

In T10540#212232, @PiscesKazeMGR wrote:

And I though the tutorial is only apply to subdomain :)

Closed as this is easy as changing some lines of records and we are done...

Let's get this thing end with...

And I though the tutorial is only apply to subdomain :)

If you say so...
And also I have checked the record. The nameserver is now from CF.
Looks like I'm will be fine if I done this as fast as I do.

I don't think we will need to do anything special here. The TLS certificate doesn't care who the authoritative nameserver is, and CNAME flattening doesn't introduce any concerns in terms of TLS. As long as you point the custom domain to mw-lb.miraheze.org, everything should Just Work.

Have you read https://meta.miraheze.org/wiki/Custom_domains#Note_for_CloudFlare_users ?

In T10362#211172, @PiscesKazeMGR wrote:

In T10362#211165, @Reception123 wrote:

I will try to get this done soon but it could be sped up if you would find your wiki in https://archive.org/details/miraheze-wikibackups18122022.

That's if I have access to a personal computer, not having to go to Internet cafe for these technical thingy.
Beside, my wiki has been deleted for a very long time before since this backup has been uploaded. I'm actually uncertain if I can get to it myself or I will have to let you do all of these just to restore a small project that I don't have time to developing before that.

In T10362#211165, @Reception123 wrote:

I will try to get this done soon but it could be sped up if you would find your wiki in https://archive.org/details/miraheze-wikibackups18122022.

I will try to get this done soon but it could be sped up if you would find your wiki in https://archive.org/details/miraheze-wikibackups18122022.

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.

@Reception123 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, the SEO things...

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.