domain connect template for uspeedo.com

[kiritoaurora]

Description

<-- short description of the template(s) and/or reason for update -->

Type of change

Please mark options that are relevant.

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

Please mark the following checks done

• 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
• resource URL provided with logoUrl is actually served by a webserver

Example variable values

<-- to make review process easier please provide example set of variable values for this template -->

<-- Example: -->

var1: aaa
var2: foo.com

<-- Or provide the whole testData object from the Online Editor after testing and using "Add as test" button -->

"testData": {
    "testset": {
      "variables": {
        "domain": "example.com",
        "host": "foo",
        "example": "bar"
      },
      "results": [
        {
          "type": "TXT",
          "name": "foo",
          "ttl": 86400,
          "data": "\"bar\""
        }
      ]
    }
  }

[github-actions]

Linter OK:

Linter result for uspeedo.com.email.json

[kerolasa]

Could you reconsider use of %host% variable?

https://github.com/Domain-Connect/dc-template-linter/wiki/DCTL1024

[kiritoaurora]

Could you reconsider use of %host% variable?你能重新考虑使用 %host% 变量吗？

https://github.com/Domain-Connect/dc-template-linter/wiki/DCTL1024

@kerolasa I have changed the variable %host% to %subdomain%. Is that okay?

[kerolasa]

Looks good to me.

[pawel-kow]

is this host under %subdomain%?
If it is the whole template could have used @ instead of %subdomain% and standard host parameter, which has quite benefits - template can be applied several times to the same domain and different subdomains if needed.
Otherwise multiInstance setting might be of help.