Thora Cloud
A direct line to Thora

Start a conversation

What can we help make simpler?

Tell us what you need. A real person will point you to the right place.

Email Thorahello@thora.cloudExplore SupportSee the available support paths
Browse docs Connect a domain

Help and guides

Connect a domain

Add a domain you own and choose how to connect it to Thora.

Before you start

You need access to the domain and permission to manage it for the selected organization. Keep access to your current DNS provider.

Steps

  1. Open Domains and choose Add a domain you own.
  2. Enter the name in Domain you own.
  3. Choose Move my DNS to Thora or Connect to Thora services only, then choose Continue.
  4. Follow the verification and connection instructions shown for your domain.
  5. Review DNS changes before approving them. Check the domain status after applying the instructions.

What to expect

Your dashboard records the domain and its connection status. Adding it alone does not start hosting or billing.

If something goes wrong

If verification is pending, check the exact record and allow time for DNS updates. Moving DNS can affect existing services; review the records you need before changing nameservers.

Technical reference

Connect and verify ownership

Domain discovery and connection records describe Thora's recorded state. Ownership verification is not proof that DNS has propagated, TLS is active, or the application is healthy.

  • Use the server-provided ownership instructions.
  • Do not expose verification secrets in agent output, logs, or source control.
  • Re-read the connection and resolver observations after making external changes.
  • Domain search is informational and does not reserve, register, renew, or transfer a domain.

Change hosted records with a scoped agent

Read records immediately before an update or deletion. thora_dns_record_change creates, updates, or deletes records on an already hosted zone using an organization-admin DNS write credential. It binds the connection, record identity, current revision, exact change, and idempotency key. A stale revision requires a fresh read.

  • Create and update requests use bounded record type, name, content, TTL, and priority fields.
  • A scoped agent credential can execute hosted record changes immediately. DNS hosting activation still needs signed-in administrator approval.
  • Provider ambiguity is fenced for reconciliation rather than automatically retried.
  • Registration, transfer, renewal, DNSSEC, contact, nameserver, and recurring-spend changes remain separate product decisions.

Verify the route in layers

  1. Confirm the DNS action reached a terminal success receipt.
  2. Resolve the public record from more than one appropriate resolver when propagation matters.
  3. Verify TLS hostname and certificate validity.
  4. Request the intended application path without dashboard credentials.
  5. Confirm the response belongs to the expected release and does not expose a private preview.