> ## 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.

# DNS setup by provider

> Add Jobing custom-domain records in Cloudflare, GoDaddy, Namecheap, Hostinger, Squarespace Domains, Wix, Vercel, Netlify, or Route 53.

First connect the domain in [Jobing Pages](https://jobing.site/dashboard/pages#custom-domains). Keep that browser tab open so you can copy each displayed DNS record.

## Find the correct DNS provider

Your registrar is the company where you bought the domain. Your DNS provider is the company whose nameservers currently control its records. They are sometimes different.

Use the DNS dashboard where your active nameservers are managed. Common signs include:

* nameservers ending in `cloudflare.com` mean Cloudflare manages DNS;
* nameservers ending in `vercel-dns.com` mean Vercel manages DNS;
* nameservers ending in `domaincontrol.com` usually mean GoDaddy manages DNS;
* nameservers ending in `registrar-servers.com` usually mean Namecheap manages DNS.

If you are unsure, open your registrar's nameserver section or ask its support team, “Where do I edit the active DNS records for this domain?”

## Match Jobing fields to provider fields

Providers use different labels for the same information.

| Jobing    | Other common labels                      |
| --------- | ---------------------------------------- |
| **Type**  | Record type                              |
| **Name**  | Host, hostname, record name              |
| **Value** | Target, points to, answer, content, data |
| TTL       | Time to live, cache time                 |

Use **Auto**, **Default**, or the shortest available TTL during setup.

### When the provider wants a short host

Some providers add your domain automatically.

If Jobing shows `pages.example.com`, the provider may expect only `pages` in **Host**. If Jobing shows `_vercel.pages.example.com`, it may expect `_vercel.pages`.

Use `@` for the root domain when the provider requests a host. Never enter `https://`, a slash, or a page path in a DNS field.

## Cloudflare

<Steps>
  <Step title="Open DNS records">
    In Cloudflare, select the domain, then open **DNS** and **Records**.
  </Step>

  <Step title="Add each Jobing record">
    Select **Add record**, choose the displayed type, and copy its name and value.
  </Step>

  <Step title="Use DNS only">
    For `A` and `CNAME` records, turn **Proxy status** off so the cloud is gray and shows **DNS only**. An additional proxy can delay requests, hide traffic information, and interfere with verification.
  </Step>

  <Step title="Save and check">
    Save every record, then return to Jobing and select **Check DNS**.
  </Step>
</Steps>

See [Cloudflare's DNS record guide](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/).

## GoDaddy

<Steps>
  <Step title="Open the domain's DNS">
    Open **Domain Portfolio**, select the domain, then open **DNS** or **Manage DNS**.
  </Step>

  <Step title="Add the record">
    Select **Add New Record**. Choose the Jobing type and enter its name and value.
  </Step>

  <Step title="Use the short host when requested">
    For `pages.example.com`, enter `pages` in GoDaddy's **Name** field. Use `@` for the root domain.
  </Step>

  <Step title="Save and repeat">
    Add every Jobing row, including any `TXT` ownership record. Return to Jobing and select **Check DNS**.
  </Step>
</Steps>

See [GoDaddy's CNAME record guide](https://www.godaddy.com/help/add-a-cname-record-19236).

## Namecheap

<Steps>
  <Step title="Open Advanced DNS">
    Open **Domain List**, select **Manage** beside the domain, then choose **Advanced DNS**.
  </Step>

  <Step title="Add a host record">
    Under **Host Records**, select **Add New Record** and choose the Jobing record type.
  </Step>

  <Step title="Enter only the host portion">
    Namecheap adds the domain automatically. For `pages.example.com`, enter `pages`. For `_vercel.pages.example.com`, enter `_vercel.pages`.
  </Step>

  <Step title="Save all changes">
    Add every displayed record and return to Jobing to check DNS.
  </Step>
</Steps>

Remove an existing `A`, `AAAA`, `ALIAS`, `CNAME`, or URL Redirect for the same host if it conflicts. Do not remove unrelated email records.

See [Namecheap's CNAME guide](https://www.namecheap.com/support/knowledgebase/article.aspx/9646/2237/how-to-create-a-cname-record-for-your-domain/).

## Hostinger

<Steps>
  <Step title="Open the DNS zone">
    In hPanel, open **Domains**, select the domain, then choose **DNS / Nameservers**.
  </Step>

  <Step title="Add each record">
    Use the DNS zone editor to choose the type and enter the Jobing name and value.
  </Step>

  <Step title="Use the short host">
    Enter `pages` for `pages.example.com` and `@` for the root domain.
  </Step>

  <Step title="Save and verify">
    Remove only records that conflict at the exact same host. Return to Jobing and select **Check DNS**.
  </Step>
</Steps>

See [Hostinger's DNS guide](https://www.hostinger.com/support/4468886-how-to-manage-a-records-at-hostinger/).

## Squarespace Domains

Google Domains accounts were moved to Squarespace Domains. Use these steps for domains now managed there.

<Steps>
  <Step title="Open the domain">
    Open the Squarespace domains dashboard and select the domain.
  </Step>

  <Step title="Open DNS">
    Select **DNS** in the side panel and reauthenticate if requested.
  </Step>

  <Step title="Add custom records">
    Enter the Jobing **Type**, **Name**, and **Value** in Squarespace's record fields. Use the default TTL.
  </Step>

  <Step title="Save and check">
    Add every record, then return to Jobing and select **Check DNS**.
  </Step>
</Steps>

See [Squarespace's DNS record guide](https://support.squarespace.com/hc/en-us/articles/360002101888-Adding-DNS-records-to-your-domain).

## Wix

<Steps>
  <Step title="Open Domains">
    Open **Domains** in your Wix account and select the domain.
  </Step>

  <Step title="Manage DNS records">
    Select **Manage DNS records**, scroll to the required type, then select **Add Record**.
  </Step>

  <Step title="Add every Jobing record">
    Enter the displayed name and value. Use a new subdomain such as `pages` instead of changing Wix's root or `www` records.
  </Step>

  <Step title="Save and check">
    Return to Jobing and select **Check DNS** after the records are saved.
  </Step>
</Steps>

Wix may reserve `www` for a Wix website. Use `pages`, `go`, or another unused subdomain.

See [Wix's DNS record guide](https://support.wix.com/en/article/managing-dns-records-in-your-wix-account).

## Vercel DNS

<Steps>
  <Step title="Open the domain">
    In the Vercel team dashboard, open **Domains** and select the domain.
  </Step>

  <Step title="Open its DNS records">
    On the domain's settings page, find **DNS Records** or enable Vercel DNS if the domain already uses Vercel nameservers.
  </Step>

  <Step title="Add each Jobing record">
    Choose the record type and enter the displayed name and value.
  </Step>

  <Step title="Resolve project conflicts">
    If the exact domain or subdomain is already assigned to another Vercel project, remove that assignment before connecting it to Jobing. A different subdomain can remain with the existing project.
  </Step>
</Steps>

See [Vercel's DNS record guide](https://vercel.com/docs/domains/managing-dns-records).

## Netlify DNS

<Steps>
  <Step title="Open DNS">
    In the Netlify team dashboard, open **Projects**, then select **DNS** in the left sidebar.
  </Step>

  <Step title="Select the DNS zone">
    Choose the domain and select **Add new record** at the bottom of its DNS records.
  </Step>

  <Step title="Add every Jobing record">
    Choose the type, enter the name and value, then save.
  </Step>

  <Step title="Check in Jobing">
    Return to the Pages dashboard and select **Check DNS**.
  </Step>
</Steps>

See [Netlify's DNS record guide](https://docs.netlify.com/manage/domains/configure-domains/dns-records).

## Amazon Route 53

<Steps>
  <Step title="Open the hosted zone">
    In the AWS Route 53 console, select **Hosted zones**, then choose the public hosted zone for the domain.
  </Step>

  <Step title="Create a simple record">
    Select **Create record**. Use the Jobing name, type, and value. Keep **Alias** off unless Jobing specifically tells you otherwise.
  </Step>

  <Step title="Repeat for every row">
    Create the routing and ownership records, then select **Create records**.
  </Step>

  <Step title="Check in Jobing">
    Return to the Pages dashboard and select **Check DNS**.
  </Step>
</Steps>

See [Route 53's record guide](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html).

## Another provider

Look for **DNS**, **DNS records**, **DNS zone**, **Zone editor**, or **Manage DNS**. Add each row from Jobing using the field mapping near the top of this page.

Do not choose URL forwarding, framed forwarding, masking, or a website redirect. Those features do not connect the domain to Jobing.

If the provider rejects a full record name, remove the root domain from the end and enter only the host portion. If it still fails, send its support team the type, name, and value shown by Jobing. Do not send account passwords or Jobing sign-in details.

Next, [assign pages and paths](/pages/custom-domain-addresses) or solve a [domain setup problem](/pages/custom-domain-troubleshooting).