Skip to content

Add website hosting configuration for Magellan#718

Open
BaptisteLam wants to merge 3 commits intoDomain-Connect:masterfrom
BaptisteLam:master
Open

Add website hosting configuration for Magellan#718
BaptisteLam wants to merge 3 commits intoDomain-Connect:masterfrom
BaptisteLam:master

Conversation

@BaptisteLam
Copy link

Description

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

Service Provider Information

Field Value
Provider Name Magellan
Provider ID builtbymagellan.com
Service ID websitehosting
Service Name Website Hosting
Website https://builtbymagellan.com
Contact Email support@builtbymagellan.com

Template Purpose

This template enables users to connect their custom domains to Magellan-hosted websites with a single click. Magellan is a no-code website builder that allows users to create and deploy professional websites.

DNS Records Added

Type Host Value TTL
A @ 185.158.133.1 3600
CNAME www proxy.builtbymagellan.com 3600

Verification

  • TXT record _domainconnect-verification.builtbymagellan.com added
  • Template hosted at /.well-known/domain-connect/
  • Logo accessible at provided URL

Testing

Ready for testing with domains hosted at:

  • GoDaddy
  • 1&1 IONOS
  • Plesk

## 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.schema)
- [ ] Template functionality checked using [Online Editor](https://domainconnect.paulonet.eu/dc/free/templateedit)
- [ ] Template is checked using [template linter](https://github.com/Domain-Connect/dc-template-linter)
- [ ] Template file name follows the pattern `<providerId>.<serviceId>.json`
- [ ] resource URL provided with `logoUrl` is actually served by a webserver

# Checklist of common prolems of issues (mark all the checkboxes after conducting the check). Comment on any point which is not fulfilled.
- [ ] digital signatures are used and `syncPubKeyDomain` specified (yes, `warnPhishing` is an option, but some providers reject such templates by policy, so signing shall be a default)
- [ ] `syncRedirectDomain` is specified when intended to use `redirect_uri` parameter in the synchronous flow
- [ ] no TXT record with SPF content (i.e. `"v=spf1 ..."`) instead of using SPFM record type on APEX
- [ ] `txtConflictMatchingMode` is set on TXT records which shall be unique on a label (like DMARC)
- [ ] variables are set to the smallest scope needed (i.e. limit possibility to be misused to set any arbitrary record and conflict with other template). Too broad scope example: @ TXT "%verification%". Better usage: @ TXT "foo-verification=%verification%".
- [ ] no variables as a host name to apply template on subdomain instead of standard `host` parameter
- [ ] no explicit usage of `%host%` variable in `host` attribute 
- [ ] `essential` setting is used on records, which the user shall be able to change or remove manually later without dropping the whole template (like DMARC)    

# 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](https://domainconnect.paulonet.eu/dc/free/templateedit) 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
Copy link

github-actions bot commented Jan 15, 2026

Linter OK:

Linter result for builtbymagellan.com.website.json

@pawel-kow
Copy link
Member

Please fill in the PR template description properly including all checklists.

@pawel-kow pawel-kow added the PR description incomplete The PR description template was not filled in at all, altered or filled in improperly. label Jan 16, 2026
….website.json

fix: rename to website.json and update syncRedirectDomain to string
@BaptisteLam
Copy link
Author

BaptisteLam commented Jan 16, 2026

Description

This PR adds a Domain Connect template for Magellan, a no-code website builder SaaS. The template enables one-click custom domain configuration by automatically setting up the required DNS records (A and CNAME) to point to Magellan's hosting infrastructure.


Service Provider Information

Field Value
Provider Name Magellan
Provider ID builtbymagellan.com
Service ID website
Service Name Magellan Website Hosting
Website https://builtbymagellan.com
Contact Email support@builtbymagellan.com

Template Purpose

This template enables users to connect their custom domains to Magellan-hosted websites with a single click. Magellan is a no-code website builder that allows users to create and deploy professional websites. The template automatically configures:

  • An A record pointing the apex domain to Magellan's proxy server (185.158.133.1)
  • A CNAME record redirecting www subdomain to proxy.builtbymagellan.com

DNS Records Added

Type Host Value TTL
A @ 185.158.133.1 3600
CNAME www proxy.builtbymagellan.com 3600

Verification

  • TXT record _domainconnect-verification.builtbymagellan.com added with value domain-connect-template-v1
  • Template will be hosted at https://builtbymagellan.com/.well-known/domain-connect/builtbymagellan.com/website.json
  • Logo accessible at https://builtbymagellan.com/lovable-uploads/magellan-logo-dark.png

Testing

Ready for testing with domains hosted at:

  • GoDaddy
  • 1&1 IONOS
  • Plesk
  • Cloudflare (synchronous flow only)

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>.jsonbuiltbymagellan.com.website.json
  • Resource URL provided with logoUrl is actually served by a webserver

Checklist of common problems of issues

  • Digital signatures: Not using variables in this template, so warnPhishing: true provides adequate security. If variables are added later, we will implement proper signing with syncPubKeyDomain.
  • syncRedirectDomain is specified: Set to "builtbymagellan.com,app.builtbymagellan.com" to allow redirect_uri callbacks
  • No TXT record with SPF content: Not using SPF records in this template
  • txtConflictMatchingMode: Not applicable (no TXT records with variables)
  • Variables scope: No variables used - all records are static
  • No variables as host names: Not applicable (no variables)
  • No explicit %host% variable: Not applicable (no variables)
  • Essential setting: Not applicable (static records users shouldn't modify)

Example variable values

No variables are used in this template. All DNS records are statically defined with fixed values.

Test data for Online Editor verification:

{
  "testData": {
    "default": {
      "variables": {
        "domain": "example.com"
      },
      "results": [
        {
          "type": "A",
          "name": "@",
          "ttl": 3600,
          "data": "185.158.133.1"
        },
        {
          "type": "CNAME",
          "name": "www",
          "ttl": 3600,
          "data": "proxy.builtbymagellan.com"
        }
      ]
    }
  }
}

Additional Notes

  • This is a simple, secure template with no user-provided variables
  • Static DNS configuration minimizes security risks
  • TTL set to 3600 seconds (1 hour) for reasonable propagation time
  • Both apex (@) and www subdomain are configured for complete domain coverage

@pawel-kow
Copy link
Member

Description in the last comment is fine, but actually you need to update the first comment/PR description which goes then into merge commit comment.

@ysuniltechovarya
Copy link
Contributor

How long does GoDaddy typically take to synchronize approved Domain Connect templates? @pawel-kow

@pawel-kow
Copy link
Member

@ysuniltechovarya I can't provide information about DNS provider's process.
Contacting them is the process https://www.domainconnect.org/dns-providers/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR description incomplete The PR description template was not filled in at all, altered or filled in improperly.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants