Have you added your custom domain to Kanorio, but it still shows "Waiting for DNS to take effect"? This usually doesn't mean your website is broken; it means your DNS settings are propagating or there is a small detail that needs adjustment.
This guide explains DNS, SSL certificates, and common errors in plain language, helping you troubleshoot step-by-step.
Think of DNS as the phonebook of the internet.
People remember URLs like yourbrand.com, but computers need to know which service to go to. A DNS record is an entry in this phonebook that tells browsers: "When someone enters this URL, go to the Kanorio website service."
You don't need to understand every DNS type. When connecting to Kanorio, these are the most common ones:
| Name | Plain English Meaning | Purpose for Kanorio |
|---|---|---|
| CNAME | Alias or signpost for a URL | Points www or subdomains to the Kanorio target. |
| A Record | Server address for a URL | Used when a provider doesn't support CNAME for root domains. |
| MX Record | Signpost for receiving email | Used for business email; do not delete when setting up a website. |
| TXT Record | Field for verification or text settings | Commonly used for domain verification and email security. |
| CAA Record | Rules for certificate issuance | May affect whether SSL certificate setup can complete. |
DNS does not update globally in the same second. Network services and devices cache old data for a while before re-querying new settings. This process is called DNS propagation.
Common timeframes:
During this wait, you might see:
These phenomena don't necessarily mean your settings are wrong. Please check that your records are correct and give DNS some time.
After you save your custom domain in site management, Kanorio creates a verification process to confirm:
When the management page is open and there are no unsaved changes, the system periodically re-checks pending domains. Published sites are also continuously retried by background tasks. You do not need to repeatedly delete and re-add the same domain.
| Status | What it means | What you should do |
|---|---|---|
| Waiting for DNS | Domain saved, but DNS or SSL not ready. | Check records and wait. |
| Active | DNS and SSL are ready. | Test with an incognito window. |
| Verification failed | System cannot confirm current settings. | Troubleshoot using this checklist. |
If a pending custom domain remains unverified for more than 7 days, the system will clear the pending configuration. After fixing your DNS, please re-add the domain and save again.
An SSL certificate enables https:// for your URL and displays a padlock in the browser. Simply put, it encrypts data sent between visitors and your website, preventing it from being easily read or tampered with in transit.
Kanorio automatically configures SSL certificates for successfully connected custom domains; you don't need to buy or upload one separately.
Correct DNS does not guarantee instant SSL completion. After DNS passes, the certificate may still take minutes to hours to enable. During this time, keep your DNS records unchanged and use your free Kanorio URL to continue testing.
If your URL won't open, shows the old site, or is stuck in a pending state, follow these steps.
Ensure you added:
yourbrand.comwww.yourbrand.comshop.yourbrand.comDo not enter:
https://yourbrand.comyourbrand.com/aboutwww (missing the full domain)Root domains and www are different URLs. If you only added www.yourbrand.com, don't expect yourbrand.com to open automatically.
Your domain might be purchased from Service A, but DNS is managed by Service B. A common example: domain bought from Namecheap or GoDaddy, but nameservers changed to Cloudflare.
In this case, edit DNS in Cloudflare, not at the original registrar. If unsure, check "Nameservers" in your domain account or ask the person who manages your domain.
Go back to the custom domain section in Kanorio and compare every field:
@, www, or the correct subdomain prefix?https://, slashes, spaces, or typos?www records?Generally, the CNAME target is saas.kanorio.com. If your root domain provider doesn't support CNAME, use the A record method as described in .
If a name previously pointed to an old host, there might be old A, AAAA, or CNAME records conflicting with the new ones.
Only address conflicts for the same site name:
www, check if there are other www A, AAAA, or CNAME records.If unsure about a record's purpose, take a screenshot, note the original value, and ask your original site vendor, IT staff, or support.
DNS caching can cause the same computer to see old results temporarily. Try these in order:
If only one device is acting up, it's likely that device's or network's cache hasn't updated yet.
If www.yourbrand.com opens but yourbrand.com doesn't (or vice-versa), one of the full URLs is missing a record or hasn't been added to Kanorio.
Ensure both URLs are:
Wait a few hours. If it's still showing a certificate error after 24 hours, check:
CAA is a security rule restricting certificate authorities. Do not delete existing company CAA records; have your domain security manager confirm, or provide the record content to support for help.
You can use WhatsMyDNS to see if new DNS records have propagated in different regions.
Note:
saas.kanorio.com directly.Cloudflare DNS records can use proxy mode. In proxy mode, external DNS queries might not see the original CNAME, but traffic may still reach Kanorio correctly.
Don't turn off Cloudflare's orange cloud just because you're binding to Kanorio. First, ensure record names and targets are correct, wait for verification, and then troubleshoot based on actual errors. If your company has security, caching, or firewall rules, check with your administrator before changing anything.
Contact support directly in these cases to avoid creating more conflicts through repeated attempts:
When contacting us, please provide:
www, or another subdomain.Please do not provide account passwords, API keys, credit card numbers, or verification codes for your DNS backend.
www significantly at once, it's harder to identify the source of an error.Usually minutes to a few hours, up to 24-48 hours. Provider settings, caching, and nameservers affect speed.
No need. Kanorio automatically configures SSL after successful domain verification. If the certificate isn't ready, check DNS and CAA settings first; no need to buy one separately.
Not necessarily. Kanorio handles common proxy scenarios. If verification fails for a long time, check your record content and Cloudflare DNS status first.
External tools only show partial DNS propagation. Confirm the status in Kanorio is "Active" and wait for SSL to enable; also try an incognito window and mobile data.
Different devices and networks use different DNS caches. Try an incognito window, restart your browser, or switch networks; it usually resolves as propagation completes.
Only if you delete or overwrite email records. Keep MX, SPF, DKIM, and DMARC records when setting up your site.
Not necessarily. If the whole domain is down, check DNS first. If only a specific path (e.g., /old-page) is broken, the page path might have changed, or you need to set up URL redirects. Read Setting up URL redirect rules.