Set up a custom domain

The value is not a valid hostname: it contains https://, a path, a space or other disallowed characters, has only one part, is an IP address or exceeds 253 characters. Enter only the hostname, for example www.example.com.

The hostname is in a zone no project may use: teisenda.com or teisendapages.com. Use your own domain.

The hostname is in the teisendahosting.com zone where TEISENDA assigns TEISENDA addresses. Use your own domain; the project's TEISENDA address needs no entry.

The domain already leads to a project: this one, another in the Space, another Space's project, or one known to the hosting node. It stays assigned until removed from the other project. After project deletion, it becomes available when the node confirms deletion. Remove it there first or use another hostname.

The project already has 19 custom domains. Remove one you no longer need.

The Space has as many custom domains as its plan allows projects, counted across all projects. TEISENDA added nothing. Remove a domain. A larger plan allows more projects and therefore domains: Plans.

• After checking in the wizard: the domain's DNS is not correct yet. The rows below show what the hosting node found. Correct records with your DNS provider, wait a few minutes and click Check again.
• In the address table below the domain status, and at the top of the DNS-record step, as the saved result of an activation attempt: DNS was incorrect at that time, so the node requested no certificate. Open the wizard, check DNS and activate again.

• The wizard requested the records, but the hosting node did not respond. The wizard asks only once. Click Check DNS to ask the node again.
• The node did not respond when adding, checking, activating or fetching status. Retry the step in a few minutes.

Adding, checking, activating or fetching status did not reach the hosting node, or the node rejected it. After adding, the domain is still saved in TEISENDA. Another sentence may replace this one: If sending fails. Retry the step in a few minutes.

The domain has no DNS record pointing anywhere. Set the CNAME or A record shown by the wizard.

The A record expected by the hosting node is missing. Set it to the shown value, or use the CNAME record instead.

Besides the correct A record, another points elsewhere. Remove the other A record with your DNS provider.

The domain points to a server other than the hosting node. Replace its CNAME or A record with the one shown.

The domain has an AAAA record pointing elsewhere; IPv6 visitors would not reach the website. Remove it, or set it to the shown value if the wizard gives one.

A CAA record prevents the hosting node's certificate authority from issuing a certificate. Change or remove it with your DNS provider to allow Let’s Encrypt.

Ownership proof is missing: the TXT record is absent or has a different value. Set the name and value shown in Proof of ownership.

The domain's DNS does not respond, so the node could not check anything. Work with your DNS provider to make the domain resolve, then check again.

The node's two resolvers do not both see the records yet. Wait a few minutes and check again.

The certificate authority rejected this domain's certificate. Check DNS records, especially CAA, and activate again. If the message remains, contact support.

The hosting node reports a problem with no specific interface message, such as a node restart interrupting certificate issuance. Check and activate again. The app also restarts interrupted issuance automatically.

Yes, at any step. A domain not yet active has Continue setup in its row, which reopens the wizard. You cannot return to an earlier step.

• Address: a CNAME and an A record, choose one, plus AAAA if specified by the node. They point the domain to the hosting node.
• Proof of ownership: a TXT record with the name _teisenda-hosting.<Domain> and value teisenda-hosting=<Nachweis>.
• The hosting node checks DNS with two public resolvers, and both must see the same: the correct address, no second A record and no AAAA pointing elsewhere. A CAA record must not prohibit the certificate.

On activation, the hosting node obtains certificates one at a time. Other domains wait as Pending until their turn. The node renews certificates itself.

• Automatic address: the project's TEISENDA address. Primary domain: the address where TEISENDA serves the website.
• Pending: the domain is added to the project, but the hosting node does not serve it yet because it has no certificate. Every domain starts this way.
• Active: The hosting node considers the domain active. The separate certificate indicator shows whether its certificate is valid. An active domain can also report a missing certificate; the app then retries issuance during automatic reconciliation.
• Failed with Certificate rejected: the last certificate attempt failed; the reason appears below.
• The table can lag between refreshes. While a domain is not active or its certificate is not valid, the app fetches status automatically about every five minutes.
• The certificate has No certificate yet, Certificate being issued, Certificate valid or Certificate rejected.

The domain is not active yet. The row menu's entry is disabled with Only possible once the domain is active. on a second line. Finish setup first using Continue setup in its row.

This is not a rejection: the change is saved in TEISENDA, but the hosting node has not accepted it. Visitors still see the previous state. Wait about five minutes or send it yourself: Send the current state again.

While a custom domain is primary, the TEISENDA address's row has Set as primary domain. A project has exactly one primary domain.

It stays selected in the app. The hosting node redirects to another address it serves until the certificate returns.

Yes. The hostname is available and can be added to this or another project. It starts afresh, with new ownership proof and a new certificate.