Add: easydigz.com templates for custom domain and custom email domain…

[nishantmaheshwari-ideafoundation]

… setup

Description

New templates for EasyDigz (easydigz.com), a whitelabel platform enabling real estate agencies to set up branded websites with custom domains and email configurations.

Templates:

• easydigz.com.custom-domain.json - Subdomain mapping via CNAME with domain verification
• easydigz.com.custom-domain-ssl.json - Subdomain mapping with SSL certificate provisioning
• easydigz.com.ses-email.json - AWS SES email authentication (DKIM, SPF, DMARC)

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
• Template file name follows the pattern <providerId>.<serviceId>.json

Example variable values

easydigz.com.custom-domain.json

host: www
target: proxy.easydigz.com
verificationToken: cf-verification-abc123

easydigz.com.custom-domain-ssl.json

host: www
target: proxy.easydigz.com
verificationToken: cf-verification-abc123
acmeChallenge: dnsauth.abc123xyz

easydigz.com.ses-email.json

dkim1Selector: abcdef1234
dkim1Value: abcdef1234.dkim.amazonses.com
dkim2Selector: ghijkl5678
dkim2Value: ghijkl5678.dkim.amazonses.com
dkim3Selector: mnopqr9012
dkim3Value: mnopqr9012.dkim.amazonses.com
mailFromSubdomain: mail
mailFromMx: feedback-smtp.us-east-1.amazonses.com
spfValue: v=spf1 include:amazonses.com ~all
dmarcValue: v=DMARC1; p=none;

[github-actions]

Linter OK:

Linter result for easydigz.com.custom-domain-ssl.json
Linter result for easydigz.com.custom-domain.json
Linter result for easydigz.com.ses-email.json

[kerolasa]

Could you reconsider %host% variable? Ref: https://github.com/Domain-Connect/dc-template-linter/wiki/DCTL1024

[pawel-kow]

Please just read the specification how host parameter gets resolved.
Use of @ character shall be a hint.

[kerolasa]

Looks good to me. And just as a heads up, many DNS providers use synchronous flow which means you might need to add syncPubKeyDomain sooner or later to your templates.

[nishantmaheshwari-ideafoundation]

Please just read the specification how host parameter gets resolved. Use of @ character shall be a hint.

Initially we are targeting subdomain only, reason being that we used that variable %subdomain-prefix%

If we use @ instead of %subdomain-prefix%, then this will resolve with ?host=www or ?host=anysubdomain
then, can you please confirm if this will be also resolved like below (Lets assume, @=www):

{ "host": "_cf-custom-hostname.@"} to { "host": "_cf-custom-hostname.www"}

[pawel-kow]

Please just read the specification how host parameter gets resolved. Use of @ character shall be a hint.

Initially we are targeting subdomain only, reason being that we used that variable %subdomain-prefix%

If we use @ instead of %subdomain-prefix%, then this will resolve with ?host=www or ?host=anysubdomain then, can you please confirm if this will be also resolved like below (Lets assume, @=www):

{ "host": "_cf-custom-hostname.@"} to { "host": "_cf-custom-hostname.www"}

All "host" entries are relative to the template application fqdn. So ".@" is not needed and not even generally accepten. Just use "_cf-custom-hostname". Use "@" if no sublabel is needed.

[nishantmaheshwari-ideafoundation]

Please just read the specification how host parameter gets resolved. Use of @ character shall be a hint.

Initially we are targeting subdomain only, reason being that we used that variable %subdomain-prefix%
If we use @ instead of %subdomain-prefix%, then this will resolve with ?host=www or ?host=anysubdomain then, can you please confirm if this will be also resolved like below (Lets assume, @=www):
{ "host": "_cf-custom-hostname.@"} to { "host": "_cf-custom-hostname.www"}

All "host" entries are relative to the template application fqdn. So ".@" is not needed and not even generally accepten. Just use "_cf-custom-hostname". Use "@" if no sublabel is needed.

Got it, i found that is automatically resolved, when we go with host as @ and if we take ?host=www, then { "host": "_cf-custom-hostname"} automatically resolves to { "host": "_cf-custom-hostname.www"}, and rest references with same nomenclature shows same behaviour.

Please once validate my reasoning, then i will make the final changes.
Thanks @pawel-kow

[pawel-kow]

correct

[nishantmaheshwari-ideafoundation]

correct

Thanks @pawel-kow , Can this be get live now?

[pawel-kow]

If you specify "warnPhishing" and not "syncPubKeyDomain" please be aware the template may be rejected by some providers (for sure Cloudflare has such policy).

[nishantmaheshwari-ideafoundation]

Acknowledged @pawel-kow , Thanks for this information,
Can we go forward with these templates, and can we update rest in further upgrades
If possible, can this be live for now.

[pawel-kow]

ok

[pawel-kow]

ok, no template signing wished.
warnPhishing set to true

[nishantmaheshwari-ideafoundation]

ok, no template signing wished. warnPhishing set to true

@pawel-kow , Can you please assist me in mooving forward with this , like some kind of official API documentation for like godaddy for the integration, or do i need to contact them.

Do i need to contact each provider to onboard us?

[pawel-kow]

ok, no template signing wished. warnPhishing set to true

@pawel-kow , Can you please assist me in mooving forward with this , like some kind of official API documentation for like godaddy for the integration, or do i need to contact them.

Do i need to contact each provider to onboard us?

Yes contact data is here https://www.domainconnect.org/dns-providers/

[nishantmaheshwari-ideafoundation]

ok, no template signing wished. warnPhishing set to true

@pawel-kow , Can you please assist me in mooving forward with this , like some kind of official API documentation for like godaddy for the integration, or do i need to contact them.
Do i need to contact each provider to onboard us?

Yes contact data is here https://www.domainconnect.org/dns-providers/

Thanks @pawel-kow , I have mailed GoDaddy already, but does it takes time for DNS providers to sync the templates.