es.js.org

[enzonotario]

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions

[MattIPv4]

Hi there!

❌ Before we can accept your domain request, you need to configure your GitHub Pages site to use the requested js.org subdomain. Head to your repository settings, locate the Pages settings (under Code and Automation), and enter the js.org subdomain in the custom domain field. 📝

[enzonotario]

Hi there!

I tried to do so, but it says:

The custom domain `es.js.org` is already taken. If you are the owner of this domain, check out https://docs.github.com/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages for information about how to verify and release this domain.

I saw that in previous cases you mentioned contacting GitHub Support. I will contact them and get back. Thank you!

[enzonotario]

Hi there! I've contacted GitHub Support, and they've informed me that they need to verify the domain through a TXT record in the DNS. I showed them this PR to see if they could handle it from their end, but they say they require the TXT record.

Could you please assist me with this? GitHub is instructing me to:

Create a TXT record in your DNS configuration for the following hostname:
_github-pages-challenge-es-js.es.js.org

Use this code for the value of the TXT record:
64eb9dc217adba5f1cff49946b626a

Thank you!

[indus]

@enzonotario I've just added the TXT record

[indus]

I've also already added your requested subdomain to JS.ORGs zonefile. But the CNAME in your branch with the single line es.js.org is required to make it work.
I'll merge after we have "contact". Please keep this PR open.

[enzonotario]

Thanks @indus , I've added the CNAME file in the branch.

[indus]

for some reason github still redirects to a 8 year old page without content: https://es.js.org/

[indus]

Did it say something about the CNAME beeing taken this time?

[indus]

It looks like cloudflare is having some preoblems as well. Maybe it just takes some time to propagate. I will check again tomorrow.

[enzonotario]

Ok, thanks! From my end, it says that it's verified:

But ok, lets wait. I also have asked to them. Thanks again!

[indus]

No improvment! Hm - the CNAME record is in the zonefile:

and it points to es-js.github.io and not jamiedixon.github.io

@enzonotario would you mind to reach out to GH support again. I think there is something messed up on their side...

[enzonotario]

Hi there!

I've contacted GitHub Support. This is what they said:

GitHub Support Response

I can see in the screenshot on the issue you linked, they had the proxy enabled for the record. Using the proxy with GitHub Pages is not supported. Cloudflare enables their HTTP/DNS proxy feature by default, meaning GitHub isn't able to see the DNS records required to generate an HTTPS certificate. You'll need to disable this for any DNS records that point towards GitHub.
Disclaimer: Disabling the HTTP/DNS proxy may interfere with other Cloudflare services. If you use other Cloudflare services with your site, we aren't able to guarantee that these will continue working. For more help with this, I'd recommend reaching out to Cloudflare's support team.

About the redirect, once a domain is verified it can take up to 7 days for the domain to be released from it's previous repository, so that's likely why you're still seeing that.

As I can confirm that the es-js org has verified the domain, I was able to release the domain from it's previous section, bypassing this 7 day window for you automatically.

Once the CNAME record is rectified in my above steps, you should be clear to re-add the domain (if not done already) and continue with the standard process of enabling HTTPS, etc.

So far, I can see it's now returning 404, instead of the old-site that was returning previously.

[indus]

@enzonotario For me it is working now.
Welcome https://es.js.org