Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get.js.org / hx.js.org / status-hx.js.org #9516

Merged
merged 1 commit into from
Jan 21, 2025
Merged

Conversation

hifocus
Copy link
Contributor

@hifocus hifocus commented Jan 21, 2025

@indus indus changed the title Update Existing Records get.js.org / hx.js.org / status-hx.js.org Jan 21, 2025
@indus indus added change This PR/issue is regarding making a change to an existing subdomain external page This PR has a target of a site that isn't GitHub Pages labels Jan 21, 2025
@MattIPv4
Copy link
Member

cc #6910

@indus
Copy link
Member

indus commented Jan 21, 2025

I've just changed your requested subdomains in JS.ORGs zonefile. Please let me know that everything works correct.
I'll merge after we have "contact". Please keep this PR open.

@hifocus
Copy link
Contributor Author

hifocus commented Jan 21, 2025

Hi @indus - good day after many years

I can confirm the new configuration works normally

C:\Users\Huangxin>dig +short cname hx.js.org
hx-js-org.dns.huangxin.org.

C:\Users\Huangxin>curl -I https://hx.js.org
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 6710
Server: GitHub.com

@MattIPv4
Copy link
Member

MattIPv4 commented Jan 21, 2025

I must ask, why are you using dns.huangxin.org, rather than just pointing these directly at GitHub? We'd much prefer these are pointed directly at GitHub, as it makes our records more accurate and allows us to reach out to you in the repositories if the cleanup automation has an issue, and it'll make things faster with one less DNS hop which you seemed to care about in the past when you removed Cloudflare?

@hifocus
Copy link
Contributor Author

hifocus commented Jan 21, 2025

I must ask, why are you using dns.huangxin.org, rather than just pointing these directly at GitHub? We'd much prefer these are pointed directly at GitHub, as it makes our records more accurate and allows us to reach out to you in the repositories if the cleanup automation has an issue, and it'll make things faster with one less DNS hop which you seemed to care about in the past when you removed Cloudflare?

Hi, thanks for asking. I am using a custom domain since I wanted less hassle for you updating records every time I decided to try something new - for example moving from gh-pages to cloudflare or vise versa. I am not sure if this breaches any policies of JS.org (given in the past it was approved). In terms of clean up - I am readily available on GitHub and through emails, and I do strive to keep contents on my pages.

@indus
Copy link
Member

indus commented Jan 21, 2025

@indus indus merged commit db7eb6d into js-org:master Jan 21, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change This PR/issue is regarding making a change to an existing subdomain external page This PR has a target of a site that isn't GitHub Pages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants