Repository navigation
DNS Wildcard problem? #3404
Description
Problem:
https://asdfiasdfuaspdajlrg.nodejs.org/ is a valid URL. You can put anything in place of asdfiasdfuaspdajlrg.
Problem:
https://asdfiasdfuaspdajlrg.nodejs.org/ is a valid URL. You can put anything in place of asdfiasdfuaspdajlrg.
Activity
nschonni commentedon Jun 15, 2021
@nodejs/build I'm not sure if this is something on your side
bnb commentedon Jun 15, 2021
we should do something about this. +1 to fixing.
jbergstroem commentedon Jun 15, 2021
The tricky part is finding the legacy reason for why adding a wildcard in the first place. I can look around a bit.
ovflowd commentedon Mar 21, 2023
@nodejs/build we talked about this last week, right?
ovflowd commentedon Mar 24, 2023
ovflowd commentedon Jul 3, 2023
I'm transferring this to @nodejs/build as this is a CloudFlare configuration issue.
richardlau commentedon Jul 3, 2023
@jbergstroem I don't suppose you ever found out why the wildcard was added?
jbergstroem commentedon Jul 3, 2023
Unfortunately, no.
richardlau commentedon Jul 3, 2023
I've tried searches on https://github.com/nodejs/build and https://github.com/nodejs/iojs.org but couldn't find anything indicating why we have the wildcard CNAME entry for nodejs.org. In the absence of any evidence as to what it was for, I'm leaning towards removing it and seeing if anyone notices/complains.
MoLow commentedon Jul 3, 2023
I think we discussed in the TSC meeting adding a 301 redirect rule to all undefined DNS records to just redirect them to www.nodejs.org. AFAIK cloudflare has this built-in
richardlau commentedon Jul 3, 2023
Actually I think I may have a theory... in https://github.com/nodejs/build/blob/main/ansible/www-standalone/resources/config/nodejs.org?plain=1 we have a number of subdomains being redirected in nginx, e.g. docs.nodejs.org
build/ansible/www-standalone/resources/config/nodejs.org
Line 355 in 621e462
targos commentedon Jul 7, 2023
We found out yesterday that a few subdomains are (ab)used to directly access our server:
registry.nodejs.org(our old friend, the broken Artifactory setup)capacitacioni-release.nodejs.orgkdxwif.cn.nodejs.orgsticky.nodejs.orgshaikon.com.nodejs.org.Removing the wildcard should help to reduce load issues on the server.
targos commentedon Jul 12, 2023
List of
server_name(based on files inansible/www-standalone/resources/config) that are not explicitly defined in Cloudflare DNS:benchmarking.nodejs.orgdoc.nodejs.orgdocs.nodejs.orgapi.nodejs.orgdist.nodejs.orgblog.nodejs.orgrichardlau commentedon Jul 12, 2023
I think we used to have a CNAME for this but it was removed #2485
richardlau commentedon Jul 12, 2023
I've added CNAME entries for everything in #3404 (comment).
I've just removed the * CNAME entry. FTR it looked like this:
richardlau commentedon Jul 21, 2023
It looks like enabling proxy on
blog.nodejs.orgbreaks test/internet/test-dns.js: nodejs/node#48868dns.resolveCname()is returningENODATAfor any of our proxied CNAME entries.We did not have proxy enabled on the now removed
*.nodejs.orgCNAME entry that used to catchblog.nodejs.org. I've turned off proxy status just forblog.nodejs.org.