Add CariSEO Blog Hosting template

[mengfoong-dev]

Description

New Domain Connect template for CariSEO Blog Hosting - an AI-powered SEO content hosting service that helps businesses create optimized blog content.

What this template does:

• Creates a single CNAME record to connect a user's blog subdomain (e.g., blog.example.com) to app.cariseo.com
• Uses hostRequired: true so users specify their desired subdomain
• Enables one-click DNS configuration via Domain Connect protocol

Type of change

• New template
• 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?

• Schema validated using JSON Schema template.schema
• Template functionality checked using Online Editor
• Template is checked using template linter - Linter OK
• Template file name follows the pattern <providerId>.<serviceId>.json → cariseo.com.blog-hosting.json

Checklist of common problems

• digital signatures are used and syncPubKeyDomain specified
  • syncPubKeyDomain: "cariseo.com" is set
  • Public key TXT record published at dc._domainkey.cariseo.com
• syncRedirectDomain is specified when intended to use redirect_uri parameter in the synchronous flow
  • N/A - Not using redirect_uri in synchronous flow
• no TXT record with SPF content
  • N/A - Template only contains CNAME record
• txtConflictMatchingMode is set on TXT records which shall be unique
  • N/A - No TXT records in template
• variables are set to the smallest scope needed
  • No custom variables used; only standard host parameter via hostRequired: true
• no variables as a host name to apply template on subdomain instead of standard host parameter
  • Correct - Uses hostRequired: true with host: "@" pattern
• no explicit usage of %host% variable in host attribute
  • Correct - Uses host: "@" which references the host parameter properly
• essential setting is used on records
  • N/A - Single CNAME record for blog subdomain, default essential behavior is appropriate

Example variable values

{
  "testData": {
    "testset": {
      "variables": {
        "domain": "example.com",
        "host": "blog"
      },
      "results": [
        {
          "type": "CNAME",
          "name": "blog",
          "ttl": 3600,
          "data": "app.cariseo.com"
        }
      ]
    }
  }
}

Result: blog.example.com → CNAME → app.cariseo.com

[github-actions]

Linter OK:

Linter result for cariseo.com.blog-hosting.json

[pawel-kow]

Please fill PR template properly.
It will help you figure out issues.

[mengfoong-dev]

alright, apologies for the confusion, thanks for your time, i will update in a while

[mengfoong-dev]

Hi @pawel-kow,

Thank you for the feedback! I've updated the template and will update the PR description now.

Changes made:

• Removed logoUrl (was returning 404)
• Added description field for clarity
• Template uses syncPubKeyDomain: "cariseo.com" with public key verified at dc._domainkey.cariseo.com

I will update the PR description with the proper checklist format.

[kerolasa]

Looks good to me

[mengfoong-dev]

@kerolasa Thank you for the review and approval!

Regarding the %host% variable usage:

Original issue: The template initially used "host": "%host%" which triggered the DCTL1024 linter warning: "use of %host% variable name is problematic".

Fix applied (commit c45fda7):

• Changed "host": "%host%" → "host": "@"
• Added "hostRequired": true

The @ symbol tells DNS providers to use the host parameter passed during the apply flow, which is the standard pattern for subdomain CNAME templates (same approach used by approximated.app.subdomaincname.json).

The linter now passes without any warnings:

Linter result for cariseo.com.blog-hosting.json

Thank you for the quick turnaround!