DNS records for your custom domain
DNS records are settings that tell the internet where your domain points. To connect a custom domain, you add two records at your DNS provider (usually the company where you bought the domain).
QRForge shows the exact records in the Custom Domain Setup window. Open it any time from the Custom Domains list with View DNS records. Always copy the values from that window. The examples below only show the shape.
Record 1: the certificate record
Shown as STEP 1 — Prove domain ownership (add CNAME).
| Field | What to enter |
|---|---|
| Type | CNAME |
| Host / Name | starts with _acme-challenge, for example _acme-challenge.links |
| Value / Target | the value shown in QRForge |
| TTL | 300 (or your provider's lowest/automatic option) |
This record proves you own the domain, so QRForge can get a free security
certificate for it. That is what makes https:// work.
Record 2: the traffic record
Shown as STEP 2 — Point traffic to QRForge. Which type you need depends on your domain:
- For a subdomain, such as
links.example.com: a CNAME record. - For a root domain, such as
example.com: an A record.
| Field | What to enter |
|---|---|
| Type | CNAME or A, as shown |
| Host / Name | your subdomain, for example links (or @ for a root domain) |
| Value / Target | the value shown in QRForge |
| TTL | 300 |
How to enter the Host / Name
DNS providers differ:
- Most providers want only the part before your domain. For
_acme-challenge.links.example.com, enter_acme-challenge.links. Forlinks.example.com, enterlinks. - Some providers want the full name. If your provider adds your domain
automatically, do not type it twice.
links.example.com.example.comis a common mistake. - For a root domain, many providers use
@for "the domain itself".
After saving, many providers show the full name next to the record. Check it matches what QRForge shows.
Common mistakes
- Only one record added. You need both records.
- Typos in the value. Use the copy buttons in QRForge.
- An old record with the same name. A name can have only one CNAME. Delete any old CNAME or A record for the same subdomain first.
- A proxy or "CDN" switched on. Some providers can route traffic through
their own servers (for example Cloudflare's orange cloud). Then the
provider hides your record and answers with its own servers instead. Our
certificate provider cannot see the
_acme-challengerecord, so setup cannot finish. QRForge shows "Our certificate provider cannot see your CNAME record yet." And the traffic record no longer points to QRForge. Set both records to DNS only (grey cloud on Cloudflare). - A CAA record that blocks the certificate. If your domain has CAA
records, add one that allows
pki.goog. QRForge tells you if this is the problem.
How long does it take?
- Most DNS changes take effect within 15–30 minutes.
- Some providers take up to 48 hours.
- QRForge keeps checking. If the first record is not found within 72 hours, setup stops with an error. Then use Delete & Retry and start again.
After you remove a domain
Delete both records at your DNS provider: the _acme-challenge CNAME and
the A or CNAME record for the domain itself.