Add rstream.io.tunnels template#997
Merged
pawel-kow merged 1 commit intoDomain-Connect:masterfrom Apr 15, 2026
Merged
Conversation
PR Description Check PassedAll required sections are filled in correctly. Details |
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
Linter OK
|
| Level | Code | Note |
|---|---|---|
| info | DCTL1021 | missing from iana definitions |
pawel-kow
approved these changes
Apr 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
New Domain Connect template for rstream tunnels.
The template provisions two DNS records to route a custom subdomain to a customer's rstream cluster:
CNAMEon the chosen host, pointing to the customer's rstream cluster edge (%cluster%).TXTat_rstream-verifycarrying the ownership token (rstream-verify=%verifytoken%) that the rstream backend reads to confirm the domain belongs to the user before activating it.Synchronous flow, RSA-SHA256 signed. Public key published as TXT at
_dck1.rstream.io.syncRedirectDomainis set because the service usesredirect_urito send the user back to the rstream dashboard after apply.This template covers subdomains only.
hostRequired: truesignals to providers that the template is not intended to be applied without a host parameter. The technical reason is that the rstream cluster edge is currently exposed only as a CNAME target, and a CNAME record at the apex is not portable across DNS providers. Apex customers are guided through a manual ALIAS/ANAME flow in the rstream dashboard instead. Apex may become a separate template in the future once a stable anchor IP (A/AAAA) or an APEXCNAME-compatible target is available.Type of change
How Has This Been Tested?
<providerId>.<serviceId>.json(rstream.io.tunnels.json)logoUrlresource is served (https://rstream.io/images/brand/rstream-logo-square-light.svg)Checklist of common problems
syncPubKeyDomainis set (rstream.io)warnPhishingis not setsyncRedirectDomainis set (rstream.io)txtConflictMatchingMode: Prefixis set on the TXT record withtxtConflictMatchingPrefix: "rstream-verify="so re-applies replace the previous tokenrstream-verify=hostlabel —hostis@or_rstream-verifyhostis used to target a subdomain — handled via the protocolhostparameter (hostRequired: true)%host%does not appear in anyhostattributeessentialis intentionally not set — both records are service-managed and must not be edited manuallyOnline Editor test results
Editor test link(s):
Test rstream.io/tunnels example.com/api