spinlab.studio.casino: Replace APEXCNAME with CNAME for Cloudflare#905
Conversation
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
Linter OK
|
| Level | Code | Note |
|---|
e5ff81a to
b5f9233
Compare
Cloudflare does not support APEXCNAME in their Domain Connect implementation, causing the consent page to crash. Using CNAME with host "@" instead, which Cloudflare automatically flattens. Bump version to 3 to trigger auto-sync.
b5f9233 to
54195fd
Compare
Note on test link coverageThe test link provided covers the
This is the same issue reported in #876. Why CNAME
|
|
@SwartZCoding a better approach would be just to define hostRequired=true. The template would be then compliant and also usable with other providers who don't support CNAME flattening. |
Per Cloudflare team recommendation: hostRequired=true makes the template compliant with the standard schema while Cloudflare ignores the flag. This also enables proper testing in the Online Editor.
Should be good now i have add hostRequired=true, if yes please merge this asap :) |
|
@kerolasa Everything is good for merge ? |
kerolasa
left a comment
There was a problem hiding this comment.
Removing the APXEXCNAME and replacing it with @ hostname will work in Cloudflare. Cloudflare does not have support for APEXCNAME record, an attempt to apply a template with such record will simply fail.
AFAIK Cloudflare would just ignore it @kerolasa can confirm this is true.
correct.
|
@kerolasa Can you please process the merge manually because of the editor don't accept this format for Cname i can't merge by myself. Thanks by advance :) |
|
@SwartZCoding just do a test with filled in host. This works fine in the editor and the check script will pass. |
PR Description Check PassedAll required sections are filled in correctly. Details |
ec60b14
- Changed record type from A (hardcoded IPs) to CNAME pointing to plop.so - Set hostRequired: true (required by spec for CNAME with host "@", Cloudflare ignores this flag and applies CNAME flattening at apex) - Bumped version to 2 - Follows same pattern as spinlab.studio PR Domain-Connect#905 (confirmed by Cloudflare Domain Connect team) - Fixes Error 1000 for Cloudflare-to-Cloudflare domains Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Use CNAME with host:"@" and hostRequired:true instead of hardcoded A record IPs. Cloudflare applies CNAME flattening at apex and ignores hostRequired. Follows same pattern as PR Domain-Connect#905 (spinlab.studio), confirmed by Cloudflare Domain Connect team. Fixes Error 1000 for Cloudflare-to-Cloudflare domains caused by shared proxy IPs (104.21.9.9, 172.67.140.209). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
## Description Updates the plop.so.website-apex template to use a CNAME record at apex instead of hardcoded A record IPs. The previous A record IPs (104.21.9.9, 172.67.140.209) are Cloudflare shared proxy IPs that caused Error 1000 for domains also on Cloudflare. Uses CNAME with \`host: "@"\` and \`hostRequired: true\` — Cloudflare applies CNAME flattening at the zone apex automatically and ignores the hostRequired flag. This follows the same pattern as PR #905 (spinlab.studio), which was confirmed by the Cloudflare Domain Connect team. Changes: - Record type: 2x A records -> CNAME pointing to plop.so - Set hostRequired: true (required by spec for CNAME with host "@") - Version bumped to 2 ## Type of change - [ ] New template - [x] Bug fix (non-breaking change which fixes an issue in the template) - [ ] New feature (non-breaking change which adds functionality to the template) - [ ] Breaking change (fix or feature that would cause existing template behavior to be not backward compatible) ## How Has This Been Tested? - [x] Template functionality checked using Online Editor - [x] Template filename follows \`<providerId>.<serviceId>.json\` pattern - [x] Resource URL with \`logoUrl\` is served by webserver ## Checklist of common problems - [x] \`syncPubKeyDomain\` is set in every template - [x] \`warnPhishing\` is not used alongside \`syncPubKeyDomain\` - [x] \`syncRedirectDomain\` not needed (no redirect_uri) - [x] No SPF content in TXT records - [x] \`txtConflictMatchingMode\` not needed (no TXT records) - [x] No bare variables as full record values - [x] No bare variables as full host labels - [x] No variables creating subdomains in host field - [x] \`%host%\` not used in host attributes - [x] \`essential\` not needed (non-modifiable records) ## Online Editor test results plop.so.website-apex subdomain test (hostRequired=true): https://domainconnect.paulonet.eu/dc/free/templateedit?token=H4sIAOIKy2kC%2F91SYW%2FTMBD9K5E%2FgWhKljRtEwmJbgOBEB2MMYSqKro4l86Q2MZ22oaq%2Fx27bWg7ED%2BAT8ndvXt%2B7%2B42xGAtKzBI0g2RSixZgeptQVIiKyH7WpDe7%2FQUajwUbFajWjKKO%2BwKc80M%2BiBxfSyd4L3XrELvjdCG8YX3ZGJxTy1wiUozwUka2n9QDPIKr1FTxaTZ5cmV4Byp8VrRKM%2FRe4WogXHPCO%2Bg0CuF8krH%2F7DndwpaTi8rQb%2BTtIRKo808gMLiGFrAhyZ%2Fh%2B31ju%2FMsOO5xR8N23UY1dgGhVSoQpN0tiGmlc7Y1XTy%2FtUBbsOXblSCcaPvxBmdMRVJo2EQbOfbHvkpOGZHtnmPFJ0CXINdBvapqI%2B0zpm24UKJRmasa5KgoNZua1377Kx%2F3hHMDgzubbbgQmGm7RdMo7AzVzeVYRms4JgqaAZSVq2Vqm3V8vxpnO8X3CkswMDfjfdIVlCnlblrCcskGcYx9WEMQ38QFrmfQ5D4%2BYiOyjK4CBPAk7N7dI3%2FuLtHE0OtkRsGVgSZVCtoNdlu5z07vf%2FEit2xhiUWGThsGIRDP4j8KLgLo3QwSKNBP45GyTh5FgRpEDgXqM3e2sZew%2BkdELH%2B9nEd3yw0XEwmXy5XZnz%2F9SaGaby%2BlWX4CT%2BH92paPU%2BSweIF2f4CJMAxTjgEAAA%3D Note: Apex test (no host) is not applicable since hostRequired=true. Cloudflare ignores this flag and applies CNAME flattening at apex regardless — confirmed by Cloudflare Domain Connect team in PR #905. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Description
Replace APEXCNAME record with
CNAMEhost: "@"+hostRequired: truefor Cloudflare compatibility. Cloudflare does not support the APEXCNAME extension record type in their Domain Connect implementation, which causes the consent page to crash with a JS error (Cannot read properties of undefined (reading 'proxyable')).Using
CNAMEwithhost: "@"andhostRequired: trueinstead — Cloudflare automatically applies CNAME flattening at the zone apex, so a CNAME record at@is resolved to A/AAAA records transparently. Cloudflare ignores thehostRequiredflag.Version bumped from 1 to 3 to trigger Cloudflare auto-sync.
Context: Discussed with Cloudflare Domain Connect team who confirmed APEXCNAME is not supported and recommended using CNAME with
hostRequired=truefor schema compliance.Records configured:
Type of change
How Has This Been Tested?
Checklist of common problems
Online Editor test results
Editor test link(s):
Test spinlab.studio/casino example.com/sub