CNAME tutorial

Point your domain's @ and www CNAME to 302tel.com at your registrar, wait ~5–15 minutes for propagation, then on 域名电话.com complete binding via password signup or Try Domain Phone (slider + calling-code picker).

What should I know before starting?

Password signup: Sign in / Register. Trial (slider, multi-country numbers): /idntel/trial-en.html (English) · /idntel/trial.html (中文).

Full path: ① Add CNAME at registrar → ② Wait for DNS → ③ Bind domain + redirect phone on this site → ④ Visitors hit your domain and phone handoff runs. After payment, complete phone verification within 10 days (SMS or DNS TXT — see TXT verification guide).

Worked example: demo-brand.com and phone 18928943920

Same steps as the rest of this page — only the sample domain and number differ. Replace them with your own domain and mobile when you go live.

DNS (registrar): For demo-brand.com, add CNAME rows for @ and www, both targeting 302tel.com — no http:// prefix.
Wait: After ~5–15 minutes run nslookup demo-brand.com until the chain resolves toward 302tel.com.
Site: Open Sign in / Register → Create an account → enter demo-brand.com and 18928943920, set password and email, pass the slider, submit.
Check: Confirm the binding in your account list, visit demo-brand.com again, and verify phone handoff behaves as expected.

Flow: domain → phone service

Top to bottom: DNS at registrar → wait & verify → bind domain + phone on this site → visitors hit your domain and the phone handoff runs. If a check fails, follow the loop back to DNS or wait longer.

flowchart TD
  subgraph dns["1 DNS at registrar"]
    A[Log into registrar] --> B["apex @ CNAME → 302tel.com"]
    B --> C["www CNAME → 302tel.com recommended"]
    C --> D[Save records]
  end
  subgraph wait["2 Propagation"]
    D --> E[Wait ~5–15 minutes]
    E --> F{Points to 302tel.com?}
    F -->|No| G[Resolve A/AAAA clashes DNS line cache]
    G --> E
  end
  subgraph web["3 Bind on 域名电话.com (trial / password)"]
    F -->|Yes| H[Sign in / register]
    H --> I[Accept binding terms]
    I --> J[Domain + phone slider password]
    J --> K{CNAME check OK?}
    K -->|No| G
    K -->|Yes| L[Submit binding]
  end
  subgraph eff["4 Live traffic"]
    L --> M[Visitor opens your domain]
    M --> N[302tel.com phone service]
  end

Registrar quick reference: apex / root record (@)

Add one row for the bare domain (your-domain.com). Field names may differ slightly (Host, Name, Points to).

Field	Value	Notes
Host / Name	`@`	Means the apex; some panels use `@`, blank, or the domain itself.
Type	`CNAME`	Must be CNAME — not A / AAAA here.
Line / region	Default	Leave default unless you use split DNS.
Target / Points to	`302tel.com`	No `http://`, `https://`, or path — hostname only.
TTL	`600` or default	Faster refresh if you are still testing; default is fine.

Registrar quick reference: www host (recommended)

Optional but recommended so www.your-domain.com behaves the same.

Field	Value	Notes
Host / Name	`www`	Resolves `www.your-domain.com`.
Type	`CNAME`	Same as apex row.
Line / region	Default	Same as apex row.
Target / Points to	`302tel.com`	Hostname only — no protocol or slash.
TTL	`600` or default	Same as apex row.

How do I verify DNS propagation?

Wait ~5–15 minutes for global DNS caches to refresh.
Use nslookup/dig, browser fetch, or your registrar's diagnostics until the chain points toward 302tel.com.
Then complete binding on Sign in / Register or Try Domain Phone.
Visit your naked domain — phone handoff should follow your production mapping.

Troubleshooting

DNS still not updating: Remove conflicting @ A/AAAA rows; confirm you are editing the active nameservers; flush local cache (ipconfig /flushdns on Windows, sudo killall -HUP mDNSResponder on macOS).
Site says verification failed: Re-check host and target for stray spaces; try mobile data if a CDN or resolver caches oddly.
SMS code never arrives: See TXT verification guide.

Extended walkthrough with Chinese-labelled registrar UI cues: full guide (中文).