Connect a domain with records (CNAME)
How to connect your site by keeping your nameservers as they are and adding one or two records where you manage your domain.
The record method keeps your DNS at your current provider and only adds lines that point to Weekerp. Other records, such as mail, are left untouched.
In Add a site, click Is changing nameservers hard? You can connect with a CNAME instead. on the nameserver screen to continue with this method.
Lines to add
Depending on the purpose, the screen shows up to three kinds of lines.
| Line | What it does | When to add |
|---|---|---|
Certificate (CNAME _xxxx.name) |
Used to confirm security certificate (SSL) issuance. It has no effect on visitors | Together with the primary address line. If it isn't on the screen, the verification screen tells you |
| Primary address | Points your primary address to Weekerp. CNAME for www and subdomains, ALIAS for the root | Now |
| Other address (www ↔ root) | Sends the non-primary address to your primary address | On the completion screen, after the connection is done |
If you add the other address line early, that address may not open, or redirects may loop with your old hosting. Add it when the completion screen tells you to.
1. Add the records
Do this on the Connect your domain to Weekerp screen.
- Log in to your domain provider and open the DNS record settings. You can go there directly from Add it at your DNS provider on the right side of the screen.
- Add lines as shown in the table on the screen (type / name / value). Copy values with the Copy button.
- When you have added them all, click I’ve added it (or I added all N if there are several lines).
2. Verify the connection
It runs automatically in this order: DNS record check → security certificate issuance → site connection check. Records usually take effect in 1–2 minutes, and the certificate and site connection each finish within 1 minute.
If the certificate step shows To issue the security certificate, add one more line below at your domain provider., add the line from the table at your provider. Once added, the certificate is issued within 1 minute.
3. Add the last line
If you use both the root and www, the other address line appears under Finally, add this line on the completion screen. Once you add this line too, visitors who arrive at the other address are also sent to your primary address.
Notes by provider
- Cloudflare: Turn off the proxy (orange cloud) on the records you added. If it stays on, verification won't pass.
- Providers that can't connect the root address: Gabia, Cafe24, Whois, Dothome, Dotname Korea, Hosting.kr, Asadal, Inames, Megazone, GoDaddy, Squarespace Domains, Google Cloud DNS, Azure DNS, and NAVER Cloud can't put a Weekerp address on the root (
@). Choose Use www for your primary address, or switch with Move nameservers. - AWS Route 53 (root): Open the root A record, turn on Alias, choose Alias to CloudFront distribution as the route traffic target, and enter the value from the screen. If you have an AAAA alias record, change it to the same value.
- Providers that can connect the root: Namecheap, Porkbun, Cloudflare, AWS Route53, Vercel, Netlify
To change your primary address
For a root domain, you can choose your primary address again with I want to use a different address on the record screen. Changing it also changes the values you need to add, so add them again using the new values on the screen.