DNS Configuration

Overview

To use RndrKit, you need to point your domain's DNS records to RndrKit's servers. The exact records depend on your DNS provider.

All traffic to your domain is routed through RndrKit's Cloudflare CDN, which provides global edge caching, DDoS protection, and SSL — regardless of which DNS provider you use. You do not need your own CDN or Cloudflare account.

Required DNS Records

We recommend setting up both records so your site works with and without www:

TypeNameValueTTLNotes
CNAMEwwwrndrkit.ioAutoAll providers
CNAME@origin.rndrkit.ioAutoApex domain (Cloudflare, or providers that support CNAME flattening)
  • www is the canonical URL where your site is served (bot detection, pre-rendering, origin proxy).
  • @ (apex) automatically redirects visitors to the www version. Without this record, users who type yourdomain.com directly will get an error.

If your DNS provider doesn't support CNAME at the apex (@): Use an A record instead: A @ 35.153.65.36. Most modern providers (Cloudflare, Namecheap, Google Domains) support CNAME flattening and should use the CNAME record above.

Cloudflare Users (Important)

If your domain's DNS is managed by Cloudflare, there is a critical requirement:

The proxy status MUST be "DNS only" (gray cloud) on all records pointing to RndrKit. Do NOT enable the orange cloud proxy.

Why?

RndrKit runs on its own Cloudflare account. When your Cloudflare account proxies a CNAME to a domain on a different Cloudflare account, Cloudflare blocks the connection with Error 1014 (CNAME Cross-User Banned). This is a Cloudflare security restriction that cannot be bypassed.

Your site is not unprotected. All traffic still routes through RndrKit's Cloudflare CDN, which provides global edge caching, DDoS protection, and automatic SSL. "DNS only" just means your Cloudflare account is not proxying — RndrKit's Cloudflare handles everything. You get the same CDN protection as any other RndrKit customer.

Cloudflare Setup Steps

  1. Log in to the Cloudflare dashboard.
  2. Select your domain.
  3. Go to DNS > Records.
  4. Remove any existing A or CNAME records for @ and www.
  5. Add the www record:
    • Type: CNAME
    • Name: www
    • Target: rndrkit.io
    • Proxy status: DNS only (gray cloud)
  6. Add the root domain record:
    • Type: CNAME
    • Name: @ (or your domain name)
    • Target: origin.rndrkit.io
    • Proxy status: DNS only (gray cloud)
  7. Click Save on each record.

Cloudflare supports CNAME flattening at the apex, so both records can be CNAMEs.

Do not re-enable the orange cloud proxy after setup. It will cause Error 1014 and break your site. The gray cloud must stay on permanently for records pointing to RndrKit.

Non-Cloudflare Providers

GoDaddy

  1. Log in to GoDaddy and go to My Products.
  2. Find your domain and click DNS.
  3. In the Records section, click Add.
  4. Add a CNAME record for the root domain:
    • Type: CNAME
    • Name: @
    • Value: origin.rndrkit.io
    • TTL: Default
    • If GoDaddy doesn't allow CNAME at @, use an A record with value 35.153.65.36 instead.
  5. Add a CNAME record for www:
    • Type: CNAME
    • Name: www
    • Value: rndrkit.io
    • TTL: Default
  6. Click Save.

If there are existing A or CNAME records for @ or www, edit them instead of creating duplicates.

Namecheap

  1. Log in to Namecheap and go to Domain List.
  2. Click Manage next to your domain.
  3. Go to the Advanced DNS tab.
  4. Add a CNAME record for the root domain:
    • Type: CNAME Record
    • Host: @
    • Value: origin.rndrkit.io
    • TTL: Automatic
    • If Namecheap doesn't allow CNAME at @, use an A Record with value 35.153.65.36 instead.
  5. Add a CNAME record for www:
    • Type: CNAME Record
    • Host: www
    • Value: rndrkit.io
    • TTL: Automatic
  6. Click the checkmark to save each record.

Google Domains / Squarespace Domains

  1. Go to Google Domains (now Squarespace Domains).
  2. Select your domain and go to DNS.
  3. Under Custom Records, click Manage custom records.
  4. Add a CNAME record for the root domain:
    • Host name: (leave blank for root)
    • Type: CNAME
    • Data: origin.rndrkit.io
  5. Add a CNAME record:
    • Host name: www
    • Type: CNAME
    • Data: rndrkit.io
  6. Click Save.

Vercel DNS

If your domain is managed through Vercel:

  1. Go to your Vercel project settings.
  2. Navigate to Domains.
  3. Remove the existing www configuration.
  4. Go to Domains at the account level.
  5. Add a CNAME record:
    • Name: www
    • Value: rndrkit.io

Verifying DNS Propagation

After updating your DNS records, verify propagation using the dig command:

dig www.example.com CNAME +short

The output should show:

rndrkit.io.

You can also check propagation status using online tools like whatsmydns.net. DNS changes typically propagate within minutes but can take up to 24 hours in some cases.

Common DNS Mistakes

  • Cloudflare proxy enabled (Error 1014): The orange cloud must be off (DNS only / gray cloud) on all records pointing to RndrKit. This is permanent, not temporary. See the Cloudflare section above.
  • CNAME name set to domain name instead of @: In Cloudflare, entering your domain name (e.g., example) in the Name field creates example.example.com. Use @ for the root domain.
  • Conflicting records: Remove any existing A or CNAME records for www and @ before adding the RndrKit records.
  • TTL too high: If you set a high TTL previously, old records may be cached longer. Lower the TTL before making changes, wait for the old TTL to expire, then update.

Next Steps

After configuring DNS:

  1. Wait for propagation (check with dig or whatsmydns.net).
  2. Verify your SSL certificate is active -- see SSL Verification.
  3. Test bot rendering with a curl command to confirm everything is working.

Previous

Adding Domains

Next

SSL Verification