runs-on.devClaim yours

Docs / Guides / Vercel

Vercel

you.runs-on.dev serving a Vercel project, over HTTPS, via CNAME.

The record

domains/you.json

"records": { "CNAME": "<hash>.vercel-dns-017.com" }

That is a shape, not a value to copy. Vercel issues most projects their own target of the form <hash>.vercel-dns-017.com, and shows it in the Domains tab once you have added the name there. Some accounts get the generic cname.vercel-dns.com instead. Either way the only correct target is the one your own Domains tab shows, so do that step first and paste what it gives you. Leave off any trailing dot: example.com. fails the hostname grammar, example.com passes.

A target belonging to a different project resolves perfectly well and serves nothing, because Vercel never routes the name to you. The record looks correct, the claim looks live, and the daily health check is what eventually notices. Guessing the target is the most common way a Vercel claim ends up stuck.

Steps

Two ways to apply this. The quickest is runs-on.dev/manage: sign in, pick the record type, paste the value, save. It writes the same commit to the registry and DNS follows within seconds. The steps below do it by pull request instead, which is what you want if you would rather review the change first. Either way handles subdomains entries.

  1. In the Vercel dashboard, first: your project → Settings → Domains → add you.runs-on.dev. Vercel then shows you the DNS it wants. Usually that is a CNAME alone. If it also shows a TXT record, read the next section before adding anything.
  2. Copy the CNAME target it shows you. That value is what goes in your record.
  3. Fork the registry and edit domains/you.json, using the target you just copied.
  4. Open a pull request. Once merged, the CNAME is synced to DNS automatically.

If Vercel also asks for a verification TXT

Vercel sometimes asks you to prove you control the domain, and shows a TXT record whose value starts with vc-domain-verify=. It belongs at _vercel.you.runs-on.dev, one label below your name, which is what the subdomains key is for:

domains/you.json

{
  "records": { "CNAME": "<hash>.vercel-dns-017.com" },
  "subdomains": {
    "_vercel": {
      "TXT": ["vc-domain-verify=you.runs-on.dev,PASTE-YOUR-TOKEN"]
    }
  }
}

Do not put that TXT beside the CNAME in records. A name carrying a CNAME cannot carry any other record type, which is a DNS rule rather than something this registry chose, and the record will be rejected. Under subdomains it is a different name, so the two coexist happily.

The record form sets this without a pull request: add a subdomain row, label it _vercel, pick TXT, and paste the value.

The registry mirrors that TXT to _vercel.runs-on.dev · the zone-level host Vercel actually reads the challenge from, since the apex itself sits in a Vercel account · automatically on every DNS sync. You only ever manage the subdomains entry above; the zone-level copy is how the registry completes the handshake.

How to tell it worked

The Domains tab in Vercel shows a green "Valid Configuration" once DNS has propagated and the certificate is issued, usually within a few minutes of the record landing. Visiting https://you.runs-on.dev should then serve your project. If it stays on "Invalid Configuration", check the CNAME target character for character against what the Domains tab shows.