> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jobing.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom domains

> Publish Jobing pages on a domain you own without losing their Jobing addresses.

A custom domain replaces a Jobing address in the link you share with customers.

For example, a page at `freshmart-job-application.jobing.online` can also appear at `pages.freshmart.com/jobs`.

<CardGroup cols={2}>
  <Card title="Connect a domain" icon="link" href="#connect-a-domain">
    Add the domain, copy its DNS records, and wait for verification.
  </Card>

  <Card title="Set each page address" icon="route" href="/pages/custom-domain-addresses">
    Choose the connected domain and a short path for every page.
  </Card>
</CardGroup>

## Choose the safest address

Use a dedicated subdomain when you already have a website:

* `pages.example.com`
* `go.example.com`
* `apply.example.com`
* `campaigns.example.com`

You can then publish several pages at addresses such as:

* `pages.example.com/contact`
* `pages.example.com/summer-offer`
* `pages.example.com/jobs`

<Warning>
  Connecting the root domain `example.com` sends that domain's website traffic to Jobing. If another website already uses it, that website may stop loading. Use a subdomain unless you want Jobing to serve the entire domain.
</Warning>

DNS connects a whole domain or subdomain. It cannot send only `example.com/campaign` to Jobing while another provider serves the rest of `example.com`. That arrangement requires a reverse proxy configured by the provider that already hosts the website.

## Before you start

You need:

* a Starter or Business plan;
* access to the account that manages the domain's DNS records;
* a domain or subdomain that is not already assigned to another hosting project;
* permission from the domain owner if you manage it for a client.

<Tip>
  The company where you bought the domain may not manage its DNS. If the domain uses Cloudflare, Vercel, Netlify, or another provider's nameservers, add the records there instead of at the registrar.
</Tip>

## Connect a domain

<Steps>
  <Step title="Open Pages">
    Go to [Pages](https://jobing.site/dashboard/pages) and find **Custom domains**.
  </Step>

  <Step title="Enter only the domain">
    Enter a value such as `pages.example.com`. Do not include `https://`, a page path, a port, or a wildcard.
  </Step>

  <Step title="Select Connect domain">
    Jobing reserves the domain for your workspace and shows the exact DNS records it needs.
  </Step>

  <Step title="Add every displayed DNS record">
    Open your DNS provider. Copy the **Type**, **Name**, and **Value** shown by Jobing. See [instructions for common providers](/pages/custom-domain-providers).
  </Step>

  <Step title="Wait for DNS to update">
    Changes often appear within minutes, but some providers and cached records can take up to 48 hours.
  </Step>

  <Step title="Check the domain">
    Return to Jobing and select **Check DNS**. When the status becomes **Live**, HTTPS is ready automatically.
  </Step>
</Steps>

<Info>
  A domain in **Waiting for DNS** or **Needs attention** counts toward your plan's custom-domain allowance. Remove an unused attempt before connecting another domain.
</Info>

## What the DNS records mean

Jobing may show more than one record.

| Record  | Purpose                                                 | What to do                                                       |
| ------- | ------------------------------------------------------- | ---------------------------------------------------------------- |
| `CNAME` | Sends a subdomain such as `pages.example.com` to Jobing | Add it exactly as shown. Do not include `https://` in the value. |
| `A`     | Sends a root domain such as `example.com` to Jobing     | Add it only if you intend Jobing to serve the root domain.       |
| `TXT`   | Proves that you control the domain                      | Add it even if the routing record already exists.                |

The values shown in your dashboard are the source of truth. Do not copy DNS values from an example, another Jobing user, or an old setup guide.

## What happens to your pages

The first custom domain you connect becomes the default domain for your workspace.

* existing pages without a custom domain are assigned to it;
* new pages use it automatically;
* each page keeps its current page ID as its initial path;
* every original `jobing.online` address continues working;
* a custom address stays offline until the domain is verified.

You can change a page's domain or path from the Pages dashboard. Learn about [page paths, assignments, and address changes](/pages/custom-domain-addresses).

## Forms on a custom-domain page

A native Jobing form continues working after its page moves to a custom domain unless the form restricts allowed websites.

If **Allowed websites** contains the old page origin, add the new origin too. Use only the HTTPS origin:

```text theme={null}
https://pages.example.com
```

Do not include `/contact` or another page path. Test one response from the live custom-domain page before sending traffic to it.

## HTTPS and certificates

Jobing requests and renews the HTTPS certificate after DNS and ownership verification succeed. You do not need to buy or upload a certificate.

Do not remove the required DNS records after the domain becomes live. Changing nameservers or DNS records later can make the custom address unavailable.

## Remove a domain

Removing a domain from Jobing:

* stops Jobing from serving its custom addresses;
* removes its assignments from your pages;
* leaves every `jobing.online` page available;
* does not delete DNS records from your provider.

After removal, delete the Jobing routing and ownership records at your DNS provider if they are no longer needed.

<Warning>
  Links using the removed custom domain stop working. Update advertisements, QR codes, emails, and social profiles before disconnecting it.
</Warning>

Continue to [DNS setup by provider](/pages/custom-domain-providers), [assign pages and paths](/pages/custom-domain-addresses), or [custom-domain troubleshooting](/pages/custom-domain-troubleshooting).