Bind a Custom Domain
A domain is the address visitors use to access your website. This article walks you through the entire process from binding to HTTPS taking effect, in operation order.
Overall Flow
Binding a domain has four steps in total. Whether steps 2 and 3 require manual operation depends on where your domain is managed:
① Bind domain → ② DNS verification (TXT record) → ③ Domain resolution (CNAME record) → ④ HTTPS certificate
| Domain Situation | Manual Operation Needed? |
|---|---|
| Managed in NamesLink and NS uses NamesLink default NS | Resolution is automatic after binding, no manual configuration needed |
| Domain already managed under your account | Prompts "This domain is already managed under your account and can be directly bound to this website" |
| Domain registered/managed on another platform | Need to manually configure TXT verification + CNAME resolution |
Step 1: Bind the Domain
Entry Point
Both locations can access it:
- Site top navigation bar → Bind Domain
- Management backend → Domain Management → Bind Domain
Interface Description
The popup title is "Bind Domain," with the prompt:
Which domain do you want to connect this website to? A domain is your website's network address for others to access. You can register a new domain or use a domain you already own.
Two Methods
Method 1: Register a New Domain
- Enter the desired domain keyword in the search box (placeholder:
Please enter a domain, e.g., www.nameslink.com). - The system displays search results and registration availability.
- Select the duration (e.g., 1 year).
- Click "Purchase Now."
If you do not have a domain yet, the page also shows a "Don't have a domain yet? Go to purchase" entry.
Method 2: Use Your Own Domain
- Enter the full domain in the "Own Domain Address" input box.
- The system performs availability verification.
Domain Verification Result Descriptions
The system verifies the current occupancy status of the domain. Possible results:
| Prompt | Meaning | Handling |
|---|---|---|
| This domain is already managed under your account and can be directly bound to this website | Domain is in your account | Can bind directly, usually automatic resolution |
| This domain is already bound | Already bound to current site | No repeated operation needed |
| This domain is already bound to another site. Unbind it from the other site first. | Occupied by your other site | Unbind from that site first |
| Domain registered on another platform, resolution required | Domain registered elsewhere | Can bind, but manual resolution configuration needed |
| Domain query exception, please retry | Query interface temporary exception | Retry later |
Overwrite Existing Binding
If the domain is already used on another website, a "Bind Domain Reminder" popup appears:
Confirm to delete this domain already used on another website? After binding this domain, the original website will no longer be accessible through this domain.
⚠️ Before confirming, please be aware: the original website will no longer be accessible through this domain.
Other Possible Binding Errors
| Prompt | Handling |
|---|---|
| Incorrect domain format | Check spelling and enter the full domain (e.g., example.com) |
| Cannot add reserved domain | This domain is on the platform reserved list and cannot be bound |
| Bound domain limit exceeded: N, cannot add more | Reached plan limit; unbind unused domains or upgrade plan |
| This domain is already bound to another CDN account | Submit a CDN ticket to release occupancy before retrying |
| CNAME resolution record already exists for this domain; please unbind first | Go to DNS provider and delete conflicting CNAME record |
| This domain is currently being configured, please retry later | Previous operation still in progress, wait for completion |
| App instance status does not allow domain binding | Check site status (expired/stopped/released) |
After successful binding, it shows: Domain bound successfully, pending resolution.
Step 2: DNS Verification (Add TXT Record)
Applicable situation: Domains not under this account.
For domains not under this account, please complete DNS resolution verification first.
The purpose of this step is to verify your ownership of the domain.
Operation Steps
- Find the domain on the domain management page and click "Verify.”
- The "DNS Resolution Verification" popup shows the record to add:
| Field | Description |
|---|---|
| Record type | TXT |
| Host record | Provided by the system; click to copy (shows "Host record copied") |
| Record value | Provided by the system; click to copy (shows "Record value copied") |
- Go to your domain's DNS provider console and add this TXT record.
- Interface prompt: "Go to the DNS provider of domain {domain} to configure this TXT record"
- If unsure how to operate, click "How to configure" for guidance
- After adding, return to Linkraft and click "Click to Verify.”
- Successful verification shows "Verification successful.”
What If Verification Fails
When "Verification failed" is prompted:
Please reconfigure and click verify again.
Common reasons:
| Reason | Handling |
|---|---|
| DNS record not yet effective | TXT records take time to take effect; wait a few minutes and verify again |
| Host record or record value entered incorrectly | Use the copy button; do not type manually |
| Added under the wrong domain | Confirm you are adding it in the target domain's DNS management page |
| Multiple conflicting TXT records exist | Delete old conflicting records |
Step 3: Domain Resolution (Add CNAME Record)
This step makes the domain actually point to your website.
Case 1: Automatic Resolution
If the domain is managed in NamesLink and uses the default NS:
For domains managed in NamesLink and using NamesLink default NS, resolution is automatic after binding.
No manual operation is needed; the system completes it automatically.
Case 2: Manually Add CNAME
Applicable situation: Domains not under this account.
For domains not under this account, please add domain CNAME resolution at your purchase provider.
Operation Steps
- Find the "CNAME Resolution Record Value" column in the domain management list and copy the value.
- Log in to your domain's DNS provider console.
- Add a CNAME record and enter the copied value.
- Save and return to Linkraft, click "Resolve" or "Retry."
Conflicting Records Must Be Deleted First ⚠️
The platform explicitly prompts:
If you previously bound other hosts, you need to delete the original resolution records to avoid conflicts.
If you encounter prompts such as "DNS record conflict, please go to the domain DNS console to delete conflicting records and retry" or "Adding DNS record exception, please go to your domain's DNS console to delete conflicting record values and retry," it means conflicting records exist and must be deleted first.
Common conflict: The same host record already has another record (such as an A, MX, TXT or other record). A CNAME record cannot coexist with other records under the same host name.
Resolution Status Descriptions
The domain management list shows resolution status:
| Status | Meaning |
|---|---|
| Unresolved | Resolution not yet configured; click "Resolve" |
| Resolving | Taking effect; prompt "Approximately 3-5 minutes needed" |
| Resolution successful | Effective; accessible normally |
Please be patient: Resolution takes about 3-5 minutes to take effect. Do not operate repeatedly during this period.
Step 4: HTTPS Certificate
Free Certificate (Default)
After domain resolution succeeds, the system will automatically apply for and configure a free SSL certificate, and automatically renew it before expiration.
HTTPS status display:
| Status | Meaning |
|---|---|
| Configuring | Certificate application and issuance in progress; please wait |
| Enabled | HTTPS effective |
HTTPS is normally accessible about 10 minutes after publishing.
Use Your Own Certificate
If you have your own purchased certificate, click "Configure HTTPS Own Certificate" and fill in:
| Field | Description |
|---|---|
| Certificate name | Custom name for easy identification |
| Certificate content | crt or pem encoding |
| Private key | pem encoding |
All three are required; otherwise it prompts "Please fill in complete certificate information." Format errors will prompt "Certificate setting exception, please check whether the format is correct."
Certificate-Related Errors
| Prompt | Cause and Handling |
|---|---|
| Domain resolution not yet effective, unable to apply for SSL certificate | Complete step 3 resolution first, wait for it to take effect before applying |
| SSL certificate application failed | Check whether resolution is normal, retry later |
| Adding SSL verification record exception | Check DNS configuration; there may be conflicting records |
| Certificate issuance in progress, wait and retry | Normal status, just wait |
| SSL certificate renewal failed | Contact customer service |
HTTPS Enabled but Browser Still Shows "Not Secure"
The platform guidance specifically mentions this scenario:
A domain with HTTPS enabled still prompts "Not Secure" when accessed. Click to view.
Common reasons:
- Certificate just issued, not yet effective → Wait 10 minutes and retry
- Browser cached old certificate → Test in incognito mode
- HTTP mixed content exists on the page → The page references images or scripts starting with
http://. Check and change tohttps://or use resources from the platform media library
Supplementary Feature: 301 Redirect
Purpose
Automatically redirect visits from one domain to another. Typical uses:
- Redirect old domain to new domain to preserve original search engine weight
- Unify multiple domains to the main domain to avoid dispersed SEO weight
Usage Conditions and Rules
301 redirect refers to redirecting from a source domain to a target domain. This feature can only be used after the website is successfully published, and the target domain cannot be the same as the source domain. When data is modified or deleted, the 301 redirect effect takes effect after 10-15 minutes.
| Item | Requirement |
|---|---|
| Prerequisite | Website must be successfully published |
| Source domain | Domain to redirect from |
| Target domain | Redirect target |
| Limitation | Source domain and target domain cannot be the same |
| Effective time | 10-15 minutes after modification or deletion |
Entry Point
Management backend → Domain Management → 301 Redirect
When deleting, it prompts: "Are you sure you want to delete this domain redirect? It cannot be restored after deletion!"
Unbind Domain
Must Read Before Operating
Before deleting a domain, the platform prompts:
- After domain deletion, you will be unable to access this website.
- We strongly recommend modifying the CNAME resolution of this domain before deletion.
Recommended order: First modify/delete the CNAME resolution at the DNS provider, then unbind in Linkraft. This prevents visitors from accessing an abnormal page.
Limitations
- System default domains cannot be unbound (prompts "Default domain cannot be unbound").
- Domains in configuring status cannot be operated (prompts "This domain is currently being configured, please retry later").
Complete Troubleshooting Table
Look up by "symptom → cause → action":
| Symptom | Possible Cause | Handling |
|---|---|---|
| Domain won't open | Resolution not yet effective | Wait 3-5 minutes; check whether CNAME is correct |
| Domain won't open | Website not published | Publish the website first |
| Domain won't open | Site expired/released | Renew; released sites cannot be restored |
| DNS verification keeps failing | TXT record not effective or entered incorrectly | Use copy button; wait a few minutes and verify again |
| Cannot add CNAME | Conflicting record exists | Delete same-name A record or old CNAME |
| Prompt says occupied by another CDN | Domain bound to another CDN account | Submit a CDN ticket to release occupancy |
| HTTPS shows configuring for a long time | Certificate issuance in progress | Wait; contact customer service if over 30 minutes |
| HTTPS prompts not secure | Mixed content / cache | Check http resource references; test in incognito mode |
| Prompt says limit exceeded when binding | Reached plan domain quantity limit | Unbind unused domains or upgrade plan |
| 301 redirect not effective | Not yet effective time | Wait 10-15 minutes |
| 301 redirect cannot be configured | Website not published | Publish the website first |