> ## 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-domain troubleshooting

> Fix DNS verification, HTTPS, 404, form, and domain ownership problems.

Your original `jobing.online` page remains available while you fix a custom domain.

## The domain stays on Waiting for DNS

Check these items in order:

1. confirm you edited DNS at the provider named by the domain's active nameservers;
2. compare every **Type**, **Name**, and **Value** with the Jobing dashboard;
3. add all displayed records, including `TXT` ownership records;
4. remove conflicting records for the exact same hostname;
5. wait for cached DNS to update, then select **Check DNS** again.

Do not repeatedly delete and reconnect the domain. That can replace the ownership challenge and restart setup.

## The provider duplicates the domain name

Some providers automatically add the root domain.

If entering `pages.example.com` creates `pages.example.com.example.com`, change the host to `pages`. For `_vercel.pages.example.com`, use `_vercel.pages`.

## There is already a record with this name

A hostname cannot normally have a `CNAME` and another `A`, `AAAA`, `CNAME`, `ALIAS`, or forwarding record at the same time.

Remove or replace only the conflicting record at that exact host. A new `pages` record does not require deleting records for `@`, `www`, mail, or another subdomain.

<Warning>
  Do not delete `MX`, SPF, DKIM, or other email records unless they conflict at the exact hostname and your email provider confirms the change. DNS mistakes can stop email delivery.
</Warning>

## Cloudflare shows the orange cloud

Change the Jobing `A` or `CNAME` record to **DNS only** while using it with Jobing. Cloudflare should show a gray cloud.

An extra reverse proxy can interfere with ownership checks, certificates, caching, security signals, and request performance.

## The domain belongs to another Vercel project

The exact domain or subdomain is already attached to another Vercel project.

Remove that exact assignment from the old project, then retry in Jobing. You do not need to move the entire root domain when only a dedicated subdomain such as `pages.example.com` is being connected.

## The root website stopped working

You probably connected `example.com` instead of a dedicated subdomain.

1. restore the root domain's previous `A`, `AAAA`, `ALIAS`, or `CNAME` records at its DNS provider;
2. remove the root domain from Jobing;
3. connect an unused subdomain such as `pages.example.com`;
4. add only that subdomain's Jobing records.

DNS providers do not always restore deleted records automatically. Use a previous DNS export, hosting instructions, or provider support if you do not know the former values.

## HTTPS is not ready

HTTPS begins after both routing and ownership verification succeed. Confirm all DNS records first.

If DNS is correct but certificate creation still fails:

* check for restrictive `CAA` records and ask the DNS provider to allow the certificate authority required by the hosting platform;
* check whether DNSSEC is broken after a nameserver change;
* disable a proxy in front of Jobing;
* wait for old DNS answers to expire, then select **Check DNS**.

Do not purchase a separate certificate for Jobing. Certificate management is automatic.

## The custom URL shows 404

Confirm that:

* the domain status is **Live**;
* the page is assigned to that domain;
* the path exactly matches the Pages dashboard;
* the URL contains one path segment;
* the page was not deleted or renamed.

For example, `/summer-offer` and `/Summer-Offer` are not the same address.

## The page works but its form fails

If the browser reports an origin or CORS error, add the custom origin under the form's **Behavior** and **Allowed websites**:

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

Do not include the page path. Publish the form setting change and test from the live custom page, not from an editor preview.

## The old custom path stopped working

Changing a page's custom path does not create a redirect. Use the new link or change the path back. Update external links before changing a public campaign address.

## A DNS change is not visible yet

DNS updates often appear within minutes, but cached records can take up to 48 hours. A longer TTL makes old values remain available longer.

Use your provider's DNS checker or support tools to confirm that the public record matches Jobing. Do not publish private account screenshots or DNS values used for unrelated services.

## The domain works on one network but not another

Different internet providers may still have different cached DNS answers. Wait for propagation, restart the browser, and test on another network. Avoid making more DNS changes while the correct record is still spreading.

## The domain was removed by mistake

The Jobing page still works at its `jobing.online` address. Reconnect the domain, add the records currently shown by Jobing, verify it, and assign the page again.

Ownership records may change when a domain is reconnected. Use the new values from the dashboard.

## You changed nameservers

Nameserver changes replace the active DNS zone. Copy the Jobing records into the new DNS provider before or immediately after the switch. Also copy email and other business records required by the domain.

After the new nameservers are active, return to Jobing and select **Check DNS**.

## Still blocked

Send [Jobing feedback](https://jobing.site/feedback) with:

* the custom domain;
* its status in Jobing;
* the DNS provider name;
* the approximate time you last changed DNS;
* a screenshot of only the Jobing-related records.

Do not send your provider password, API token, billing details, unrelated DNS records, or customer information.