Add bw subdomain

[kyrieqq]

Website

Link: https://bwshebeihourssign.cc.cd

The site is currently live at https://bwshebeihourssign.cc.cd (an attendance signing system). Once this PR is merged and the CNAME for �w is added, the site will be accessible at https://bw.rweb.site.

Screenshot: The website is an attendance sign-in system with a clean UI showing employee check-in records.

Checklist

• I have starred the repository.
• I have read and accepted the Terms of Service.
• There is reasonable content on my site.
• I have configured a custom domain for my site.

Summary by CodeRabbit

• New Features
  • Added DNS routing for the bw hostname.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bc9a3c1d-ead8-49f2-a1f8-1aee6c1913d5

📥 Commits

Reviewing files that changed from the base of the PR and between e219849 and 85765e1.

📒 Files selected for processing (1)

• records.json

---

📝 Walkthrough

Walkthrough

Adds a cname.bw entry in records.json, mapping bw to the specified Cloudflare tunnel hostname.

Changes

CNAME record update

Layer / File(s)	Summary
Add bw CNAME record records.json	Adds the bw mapping under cname.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• katorlys/rweb.site#101: Adds entries under the same cname mapping.
• katorlys/rweb.site#119: Adds another entry under the same cname mapping.
• katorlys/rweb.site#181: Adds another entry under the same top-level cname mapping.

Suggested labels: ✅Approved

Suggested reviewers: rajeev91691, ramz-n

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the change: adding the bw subdomain CNAME entry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[katorly]

Hello! Please agree to our Terms of Service by ticking all the boxes first.

[kyrieqq]

Hi @katorly, I have updated the PR description and ticked all the boxes. I have also starred the repository. Please review when you have time. Thank you!

[katorly]

There are no content on your website or your website is not online. Please make your website accessible so we can merge your Pull Request.

[kyrieqq]

Hi @katorly, thank you for the feedback! The website is now live and accessible at https://bwshebeihourssign.cc.cd - it is an attendance signing system. Once this PR is merged and the CNAME record for �w is added, the site will also be accessible at https://bw.rweb.site. Please let me know if you need anything else!

[katorly]

Hi @katorly, thank you for the feedback! The website is now live and accessible at https://bwshebeihourssign.cc.cd - it is an attendance signing system. Once this PR is merged and the CNAME record for �w is added, the site will also be accessible at https://bw.rweb.site. Please let me know if you need anything else!

The CNAME record is already added for testing purpose. Please configure the custom domain on your side to make bw.rweb.site reachable.

[kyrieqq]

Hi @katorly, thank you! I can confirm that the CNAME for �w.rweb.site is already resolving to my Cloudflare tunnel (d34840a-ab67-4ee4-9ecd-efbfa7e96f8e.cfargotunnel.com).

However, I'm running the tunnel in token mode and need to add �w.rweb.site as a public hostname in the Cloudflare dashboard. I will configure this shortly.

In the meantime, the website content is already live and verifiable at https://bwshebeihourssign.cc.cd - it's an attendance signing system. Once I configure the ingress rule for �w.rweb.site, it will serve the same content.

Could you please keep the PR open while I configure this? Thank you!

[kyrieqq]

Hi @katorly, I have configured the Cloudflare tunnel ingress rules to serve �w.rweb.site -> http://localhost:5000 (my attendance signing system).

The DNS CNAME for �w.rweb.site is already resolving to d34840a-ab67-4ee4-9ecd-efbfa7e96f8e.cfargotunnel.com (verified via nslookup), and the tunnel is running with 4 active connections.

The website at �w.rweb.site should be accessible now or within a few minutes as DNS propagates. The same content is also currently live at https://bwshebeihourssign.cc.cd.

Thank you for your help!

[kyrieqq]

Hi @katorly, the website is now live and accessible at https://bwshebeihourssign.cc.cd (HTTP 200). It is an attendance signing system. Please verify and merge when you have time. Thank you!

[kyrieqq]

Hi @katorly, I have added bw.rweb.site to the Cloudflare Tunnel ingress rules (via API). The tunnel is now configured to route bw.rweb.site -> http://localhost:5000.

Could you please verify if https://bw.rweb.site is accessible from your side? The DNS CNAME (bw.rweb.site -> cfargotunnel.com) was already added by you, and the tunnel ingress is now configured.

Note: The site is also live at https://bwshebeihourssign.cc.cd (same backend). Thank you!

[kyrieqq]

Hi @katorly, I have created a new Cloudflare tunnel and configured everything. Could you please update the CNAME record for bw.rweb.site to point to 4d19ee7a-67ae-4ace-861b-b899438b52e1.cfargotunnel.com (the new tunnel ID)?

The previous CNAME pointed to fd34840a-ab67-4ee4-9ecd-efbfa7e96f8e.cfargotunnel.com (old tunnel). The new tunnel is healthy with 4 active connections.

Once updated, https://bw.rweb.site should be fully accessible. Thank you!

[katorly]

Updated. Please check whether bw.rweb.site is accessible or not.

[kyrieqq]

Hi @katorly,

I have updated the CNAME record for bw back to fd34840a-ab67-4ee4-9ecd-efbfa7e96f8e.cfargotunnel.com in this PR (commit 85765e1).

The previous tunnel 4d19ee7a-... has been decommissioned and is no longer running. The fd34840a tunnel is now healthy and actively serving bw.rweb.site -> http://localhost:5000 (attendance signing system). The site is also live at https://bwshebeihourssign.cc.cd.

Once this PR is merged, Gcore DNS should automatically update bw.rweb.site to point to the correct tunnel. Could you please verify and merge? Thank you!

[katorly]

It's still not responding.

[kyrieqq]

Hi @katorly,

Thank you for updating the CNAME! I've identified the root cause of why bw.rweb.site is still not responding.

The problem: cfargotunnel.com does not return any public A/AAAA records when queried via DNS. This means CNAME-to-cfargotunnel.com only works when the domain's DNS is managed by Cloudflare (Cloudflare resolves it internally to edge IPs). When the domain DNS is at Gcore (like rweb.site), the CNAME chain breaks because cfargotunnel.com has no public A records to resolve to.

Comparison:

• bwshebeihourssign.cc.cd (DNS at Cloudflare) → resolves to 172.67.166.33, 104.21.11.135 ✅
• bw.rweb.site (DNS at Gcore) → CNAME to fd34840a-...cfargotunnel.com → No A record returned ❌

Possible solutions:

1. Use Cloudflare for SaaS (Custom Hostnames) to make bw.rweb.site work with Gcore DNS
2. Change the bw CNAME target to a different tunnel endpoint that has public A records
3. Unfortunately, Cloudflare Tunnel's cfargotunnel.com CNAME approach is incompatible with non-Cloudflare DNS providers

In the meantime, the site is fully accessible at https://bwshebeihourssign.cc.cd (same backend, same tunnel).

If bw.rweb.site cannot work with Gcore DNS + Cloudflare Tunnel, I understand if you need to close this PR. The cc.cd domain serves our needs fine.

Thank you for your patience and help!

[katorly]

We're sorry, but to prevent abuse that could result in the entire domain being taken down, we currently do not support any records other than CNAME.

You may consider using another hosting provider or subdomain provider.

[katorly]

We are closing this because Cloudflare Argo Tunnel doesn't support binding subdomains when top-level domain is not added to your Cloudflare account. You may switch to other hosting platforms and apply for a subdomain again in the future.