Hey, this is a blog post about the shellcore.org issues.

On the 27th of February, I bought the domain shellcore.org to start building our own little thing so that we could put a group and personal page up for all of us. First, I added a Minecraft server to the DNS, allowing us to use a private in-game server to play on a "studio map".

Then, I talked with Jamo62 and BlueShell about the main group page and what we would use to make it; long story short, we resorted to using Google Sites for its collaborative tools. Jamo62 had his site ready from a few months ago, approx*. and so it was a matter of getting the domain added to the page. That is when we ran into issue 1, and we did find this issue out in the past when I owned the domain ytlde.com. You see, custom domains in Google Sites are managed via the Google Search Console, which requires DNS Verification to use, I had already verified the domain when starting the main group site, so the property ownership was confirmed to me.

However, as we later discovered, property ownership can only be given to one individual. When we attempted to transfer ownership to my account to create jamo.shellcore.org, we hoped that it would keep the domain valid. However, once we transferred ownership back to Jamo, the domain became invalid again. So, to solve this issue, I had to be given ownership of the Google Sites document.

So we waited until the sites were populated on our DNS. However, during the DNS Population process, I discovered that we were getting many redirect calls when visiting any of the subdomains (e.g., test.shellcore.org). So, I checked our records. After a lot of investigation, I just needed to remove the old site verification, and all of our DNS platforms began working again.

This might be one of my simplest debugging sessions ever, but the previous issue was a nightmare, but I did solve it.

Blog Post by Lewis F, Made on 28/02/25, Edited on 28/02/25 2:11pm GMT

Tags: Technical / Shellcore.org Update / Lewis Nerding Outs