Fix custom domain issues
In this article: How to identify and resolve the most common problems when your Ruzuku Pro custom domain isn't working, from DNS records to SSL certificates. Pro
When to use this article
You've set up a custom domain for your Ruzuku Pro site (like courses.yoursite.com), but something isn't right. Maybe the domain shows an error page, the browser warns about an insecure connection, or the domain just doesn't load at all. This article walks through each issue with a specific fix.
If you haven't set up your custom domain yet, start with Set up your custom domain first.
Your domain isn't loading at all
If you visit your custom domain and get a "site can't be reached," "DNS address could not be found," or blank page, the DNS records are likely the issue.
Step 1: Verify your CNAME record
Your custom domain needs a CNAME record pointing to courses.ruzuku.com. Here's how to check:
- Open a DNS lookup tool. You can use dnschecker.org (free, no account needed).
- Enter your full subdomain (for example,
courses.yoursite.com). - Change the record type to CNAME.
- Click Search.
What you should see: The result should show courses.ruzuku.com as the CNAME target.
If you see no results or a different target, your CNAME record is missing or misconfigured. Log into your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) and update the record:
- Type: CNAME
- Name/Host: The subdomain prefix only (for example,
coursesif your domain is courses.yoursite.com). Do not enter the full URL. - Value/Target:
courses.ruzuku.com - TTL: Leave at the default (or set to 300 for faster propagation during setup)
Step 2: Wait for DNS propagation
After creating or updating a CNAME record, it can take anywhere from 15 minutes to 24 hours for the change to spread across the internet. Most changes take effect within 1-2 hours.
You can monitor propagation at dnschecker.org. When most or all global locations show the correct CNAME target, your domain should start working.
Step 3: Confirm the domain in your Ruzuku account
Even if your CNAME record is correct, Ruzuku needs to know about your custom domain:
- Log into your Ruzuku account.
- Click your profile photo in the upper left and select Account.
- Click Site in the left sidebar.
- Enter your custom domain (the full subdomain, like courses.yoursite.com) and follow the prompts.
If you don't see the Site option, your account may not be on the Pro plan. Email support@ruzuku.com and we'll confirm your plan status.
Your domain loads but shows an SSL error
If your browser shows a warning like "Your connection is not private," "NET::ERR_CERT_COMMON_NAME_INVALID," or a padlock with a red X, the SSL certificate hasn't been issued yet or is still provisioning.
Why this happens
Ruzuku automatically provisions a free SSL certificate for your custom domain. This process starts after your CNAME record is correctly pointing to courses.ruzuku.com and can take up to a few hours.
What to do
- Confirm your CNAME is correct using the DNS lookup steps above. SSL provisioning can't start until the CNAME is in place.
- Wait 2-4 hours. SSL certificates are issued automatically once DNS is propagated. In most cases, the certificate is ready within a couple of hours.
- Clear your browser cache. If you visited your domain while the certificate was still being provisioned, your browser may have cached the error. Clear your cache or try opening the domain in an incognito/private window.
- Check after 24 hours. If the SSL error persists after a full day with a verified CNAME record, email support@ruzuku.com. We can check the certificate status on our end and re-trigger provisioning if needed.
http:// but not https://. Once the certificate is issued, both will work and HTTP will automatically redirect to HTTPS.
Your domain works, but shows old or wrong content
If your custom domain loads a different website, a parking page from your registrar, or an older version of your site, the CNAME record is probably pointing to the wrong target.
- Run a CNAME lookup at dnschecker.org for your subdomain.
- If the target is anything other than
courses.ruzuku.com, update the CNAME record at your registrar. - If you have multiple DNS records for the same subdomain (for example, both a CNAME and an A record for
courses), delete the conflicting records. A subdomain should have one CNAME record pointing to courses.ruzuku.com and nothing else.
Your old Ruzuku URLs stopped working
They shouldn't have. After setting up a custom domain, your original courses.ruzuku.com URLs continue to work and redirect to your custom domain. Students with old bookmarks or saved links won't lose access.
If an old URL isn't redirecting:
- Confirm your custom domain is working by visiting it directly.
- Try the old courses.ruzuku.com URL in an incognito/private window (this rules out browser cache issues).
- If the old URL returns a 404 or error, email support@ruzuku.com with the specific URL so we can investigate.
Registrar-specific tips
DNS settings look slightly different at each registrar. Here are pointers for the most common ones:
GoDaddy
- Go to My Products and click DNS next to your domain.
- Click Add Record.
- Type: CNAME, Name: your subdomain prefix (e.g.,
courses), Value:courses.ruzuku.com, TTL: Default. - Click Save.
Namecheap
- Go to Domain List, click Manage next to your domain.
- Click Advanced DNS.
- Click Add New Record.
- Type: CNAME, Host: your subdomain prefix, Value:
courses.ruzuku.com, TTL: Automatic. - Click Save.
Cloudflare
- Go to your domain's DNS settings.
- Click Add Record.
- Type: CNAME, Name: your subdomain prefix, Target:
courses.ruzuku.com. - Set the Proxy status to DNS only (gray cloud icon).
- Click Save.
Google Domains / Squarespace Domains
- Go to DNS settings for your domain.
- Scroll to Custom records and click Manage.
- Host name: your subdomain prefix, Type: CNAME, Data:
courses.ruzuku.com, TTL: 300. - Click Save.
If your registrar isn't listed here, search their help docs for "add CNAME record" or email support@ruzuku.com with the name of your registrar. We'll walk you through it.
Quick diagnostic checklist
Run through these checks in order when your custom domain isn't working:
- Is the CNAME record set to
courses.ruzuku.com? (Check at dnschecker.org) - Is only the subdomain prefix in the Name/Host field (not the full URL)?
- Are there conflicting DNS records (A record, AAAA record) for the same subdomain?
- Has it been at least 2 hours since you created or changed the record?
- Is the domain entered in your Ruzuku account under Account > Site?
- If using Cloudflare, is the proxy set to DNS only (gray cloud)?
If you've checked all six and the domain still isn't working, email support@ruzuku.com with:
- Your custom domain (e.g., courses.yoursite.com)
- Where you registered your domain (e.g., GoDaddy, Namecheap)
- What you see when you visit the domain (error message, wrong site, blank page)
We can usually resolve domain issues within a few hours.