Add MonPetitBistro.com template#876
Conversation
PR Description Check FailedThe PR description is missing required elements. Please update it according to the PR template. Details |
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
Linter OK
|
| Level | Code | Note |
|---|
|
I think my version is fine overall, and the problem is with the linter. I found the same issue on this template, which is similar to mine. |
|
I was referring to a different PR because I was discussing it with the person who created it; it was in that PR that I mentioned the APEXCNAME name needed for manual merging. Please excuse the confusion. |
FWIW APEXCNAME is now supported in the editor: If you like Domain Connect consider supporting the project: |


Description
Add a new Domain Connect template for monpetitbistro.com to automate DNS configuration for custom domains.
MonPetitBistro is a website creation platform. Users connect their custom domains to their websites by configuring DNS records to point to our Cloudflare server (for example, edge.monpetitbistro.com). This template enables the synchronous Domain Connect flow, allowing users of compatible DNS providers to automatically configure their domain with a single click, including routing and SSL validation via delegated DCV.
Type of change
Please mark options that are relevant.
How Has This Been Tested?
Please mark the following checks done
<providerId>.<serviceId>.jsonlogoUrlis actually served by a webserverChecklist of common problems
Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.
syncPubKeyDomainis set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejectedwarnPhishingis not set alongsidesyncPubKeyDomain— the two must not appear togethersyncRedirectDomainis set whenever the template usesredirect_uriin the synchronous flow"v=spf1 ...") — use theSPFMrecord type insteadtxtConflictMatchingModeis set on every TXT record that must be unique per label or content prefix (e.g. DMARC)@ TXT "%foo%") unless necessary — prefer@ TXT "service-foo=%foo%"; if bare, justify in the PR descriptionhostfield to create a subdomain — use thehostparameter ormultiInstanceinstead%host%does not appear explicitly in anyhostattributeessentialis set toOnApplyon records the end user may need to modify or remove without breaking the template (e.g. DMARC)Online Editor test results
Editor test link(s):
There's a bug because I can only pass the tests without the APEXCNAME and with the host required.