Skip to main content

Web addresses

An environment's Web addresses page holds the names its applications answer on. Every application has a generated address that always works; a name you own is added on top of it, so nothing is unreachable while you set the name up.

This page is about where a name points. Registering, renewing or transferring a name, and the name's ownership proof, are on the company's Domains page.

Add a custom address​

The short version is Add a domain. In detail:

  1. Open the application (Applications, then the application) and choose its Addresses tab.
  2. Choose Add a custom address, enter the Domain name you own — only the name, like shop.example.com, without https:// or a path — and choose Add this address.
  3. Set the DNS record the page now shows at the company that runs your domain's DNS (where you bought the name, or your DNS host). The record shapes are under The records you publish.
  4. Choose Check DNS once the record is in place, or wait: a scheduled pass checks each waiting name for you. The check says what it found — no record yet, a record pointing somewhere else, or a name that points here but has not answered yet.

You need to control the name's DNS. You do not need to move the name's registration to us, you never give us your DNS provider's credentials, and you publish no ownership TXT record for a website or a redirect: pointing the name at our target is the proof. Mail, a registrar move and changes to a zone you do not control ask for their own proof, on their own pages.

A name belongs to one application. To serve the same site on www and the bare domain, add both names to the same application and choose one as its main address.

The page and its views​

Web addresses has four views:

  • Addresses — every custom name in the environment, its state, and the application it belongs to. Names are added, checked and removed on each application's own Addresses tab; this view lists them in one place.
  • Redirects — names that send every request somewhere else. See Send a whole name somewhere else.
  • Paths — which application answers which path under one name, for sites built from more than one application. See Configuration.
  • Path redirects — company-wide rules for redirecting selected paths on application domains.

Choosing a name and publishing it are separate​

  • Chosen — the name is recorded at once and the application is reconfigured to it, so a WordPress or Moodle site's own links and sign-in use the new name before its DNS answers. The generated address stays reachable; the application's own links are not promised to keep working on it once you have chosen a name.
  • Published — the name answers visitors, and only once Hosting has seen its DNS point here and its HTTPS certificate is ready. The page reports DNS, certificate and apply as separate facts rather than one "ready" light.

The records you publish​

The page shows only the records that point the name at your site. Nothing else is needed from your provider for a website or a redirect.

Name shapeWhat to publish
A subdomain such as shop.example.comA CNAME to the target the page shows
A root domain such as example.comYour provider's ALIAS, ANAME or CNAME-flattening feature
A root domain at a provider with no flatteningThe A (and, where shown, AAAA) records the page lists

A/AAAA addresses can change, so use the CNAME form wherever your provider supports it. Publish only the records shown for your environment: Home is IPv4 only, so it publishes no AAAA. Remove old routing records for the same name, and keep mail records such as MX and mail TXT records as they are.

What happens after you publish​

A background pass reads the name's own authoritative DNS servers, checks the published addresses answer on HTTP port 80, then requests the certificate through the standard HTTP-01 challenge and waits for it before the name serves HTTPS. If the issuer reports a failure for the current certificate, the address shows the reason and the next step. The same detail is available from hostingctl environment domains <environment-uuid>.

DNS and certificates take time, so the page shows the last check, its result and the next useful action rather than promising an instant switch.

The Addresses view names each state in the words of what you are waiting for:

  • Waiting for its DNS record — nothing has matched yet, or no check has run. Publish the record and check again. The application's Addresses tab shows what the last check found: an address that does not point here, a refused or unreachable lookup, or a stale record.
  • Main address or Extra address — DNS matches and the name works. A name is never shown as working because it was only chosen.
  • Being removed — the name is on its way out; see Remove a name.
  • Expiry — a name that never validates runs out of time and is released, so its owner can claim it again. A name that has validated is not on this clock; the page shows the date when one applies.

If the name was used on Hosting before​

Pointing at us proves where traffic goes, not who controls the name: a name somebody else on Hosting held before would otherwise look the same as your own. Taking such a name needs an ownership proof on the company's Domains page, or a system administrator can confirm it for you. If the page asks for that, it is deliberate; Support can arrange it.

Choose the main address​

When an application has more than one name, one is its Main address — the address visitors are sent to. Working names that are not the main one stay as Extra address entries, so existing links keep working.

Choose Use this address on the name you want visitors to land on. The application's content is not rewritten: the application is told which address it serves, and its other working names lead there.

Send a whole name somewhere else​

A name your company holds can redirect every request instead of serving an application. The Redirects view offers two targets:

  • An application's address — the name sends visitors to the main address of one of this environment's applications, and follows it if that main address changes.
  • A fixed HTTPS address — the name sends visitors to an address you type, for a name with no application here. Hosting does not manage that destination's DNS or vouch for its health.

The visitor's path and query are kept: /prices?ref=mail arrives at the same path and query on the destination. Only GET and HEAD requests are redirected; any other method is answered without being forwarded, so a request body is never replayed to another host. The source name still needs its own DNS record and certificate before it serves.

Each redirect is temporary or permanent:

  • Temporary answers are not cached, so you can change or remove the rule at any time.
  • Permanent asks browsers and search engines to remember it. A visitor's browser can keep going to the destination after you change or remove the rule, so choose it only for a final move.

A name either serves an application or redirects, never both; a conflicting choice is refused rather than silently replacing the other.

Redirect a path​

Open Web addresses → Path redirects and choose Add path redirect. Select an application and one, several, or all of its attached domains. The all-domains choice includes domains you attach later. A redirect takes effect once the domain can serve publicly.

  • Exact matches the path you enter, such as /old. Prefix also matches paths below it, such as /old/products. A prefix rule can carry that extra path to the destination.
  • Enter the destination HTTPS address. The query string is kept by default. Start with a temporary redirect. Browsers may remember a permanent redirect after you remove it.
  • Use Move up and Move down to set the order. The first matching enabled rule wins. Unmatched paths use normal application routing. Matching requests other than GET and HEAD are refused.
  • Enter a URL and choose Preview draft to see the winning rule. Choose Apply path redirects to save the whole list, then Refresh routing status to check that Hosting applied the environment generation.

To withdraw a rule, edit it and turn off Enabled, or remove it from the list, then apply the draft. You can also use hostingctl path-redirects show, preview --file, and apply --file --confirm. See the CLI reference for the command options.

Remove a name​

Choose Remove on the name, on the application's Addresses tab. The application goes back to its generated address and its other working names keep opening it. Nobody else can add the name until it has stopped answering — handing it over while it still serves your site would put their traffic on your application.

Next​

  • Register, renew or transfer the name, or prove you own it: Domains.
  • Manage the name's records when Hosting serves its DNS: DNS.
  • If a name is not routing after you publish it: Support.