EmDash Custom Domains, DNS and HTTPS
Last updated
A custom domain gives an EmDash website its public address, but connecting one involves more than choosing a name. DNS needs to direct the hostname to the application, the hosting platform needs to recognise it and HTTPS needs to work before visitors can use the site securely.
Those tasks can be handled manually when you self-host or incorporated into a managed hosting product. Understanding the pieces makes it easier to tell whether a domain is truly connected or only partially configured.
What does a domain do for an EmDash website?
The domain is the human-readable address visitors use to reach the site. It does not contain the website itself. DNS connects that name to the service responsible for answering requests, while the hosting platform routes the request to the correct EmDash application.
A site can therefore be healthy on its platform-provided address while a custom domain is still waiting for DNS changes or certificate provisioning.
What is DNS?
DNS publishes the records that tell other systems where a hostname should be handled. The exact record type and value depend on the hosting arrangement.
When connecting an existing domain, follow the records supplied by the host rather than guessing from another provider's setup. Changes can also take time to become visible through DNS caches even after the authoritative provider has accepted them.
Why does HTTPS matter?
HTTPS provides the encrypted connection between a visitor and the website. A custom hostname therefore needs a valid certificate in addition to correct DNS and routing.
A managed domain flow should not describe the site as fully connected until requests reach the intended website successfully over HTTPS. That final check is more useful than treating the creation of a DNS record as completion.
Root domains and subdomains
A business might use a root domain such as its main company address, a conventional www hostname or another subdomain. Which option is appropriate depends on the rest of the organisation's DNS and any services already using the domain.
Before changing records, identify existing email and verification records as well. Connecting a website should not require accidentally disrupting unrelated services.
Connecting a domain versus managing a domain
These are separate jobs. Connecting a domain means making a hostname you already control work with the website. Managed domains can go further into registration, transfers, renewal state and ordinary DNS administration.
DashHarbor is prioritising reliable custom-domain connection first. Broader domain and DNS management is a planned expansion where the underlying provider APIs support a clean managed workflow.
See custom-domain connection and managed domains and DNS for the DashHarbor product direction.
What should a managed EmDash host handle?
- Tell you which DNS records are required.
- Verify that the hostname belongs to the intended site.
- Provision and maintain HTTPS around the connection.
- Verify that requests actually reach the correct website.
- Keep the hosting details separate from normal content editing.
The customer may still control the domain registration itself. Managed hosting does not require transferring ownership of the domain to the website host.