DNS Configuration

Overview

To use RndrKit, you need to point your domain's DNS records to RndrKit. The exact record type depends on your DNS provider and whether you're pointing an apex domain (e.g., example.com) or a subdomain (e.g., www.example.com).

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
A@35.153.65.36AutoApex domain — works with every DNS provider
CNAMEwwwrndrkit.ioAutoAll providers
  • @ (apex) points your root domain at RndrKit so visitors who type yourdomain.com directly land on your pre-rendered site.
  • www is served the same pre-rendered content.

Apex alternative: ALIAS / apex CNAME

Some DNS providers — including Cloudflare, Route 53, DNSimple, Netlify DNS, and Vercel DNS — support CNAME flattening at the apex (sometimes exposed as ALIAS or ANAME). On those providers you can replace the A record with:

TypeNameValueTTL
ALIAS@rndrkit.ioAuto

Most registrar-provided DNS (GoDaddy, Namecheap, Google Domains / Squarespace Domains, Hostinger, etc.) does not support apex CNAME / ALIAS — use the A record above on those providers.

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 record 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 apex record (Cloudflare supports CNAME flattening, so either style works):
    • Type: CNAME
    • Name: @ (or your domain name)
    • Target: rndrkit.io
    • Proxy status: DNS only (gray cloud)
  6. Add the www record:
    • Type: CNAME
    • Name: www
    • Target: rndrkit.io
    • Proxy status: DNS only (gray cloud)
  7. Click Save on each record.

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

GoDaddy does not support CNAME at the apex. Use an A record for @ and a CNAME for www.

  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 an A record for the root domain:
    • Type: A
    • Name: @
    • Value: 35.153.65.36
    • TTL: Default
  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

Namecheap does not support CNAME at the apex. Use an A record for @ and a CNAME for www.

  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 an A Record for the root domain:
    • Type: A Record
    • Host: @
    • Value: 35.153.65.36
    • TTL: Automatic
  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

Squarespace Domains (formerly Google Domains) does not support CNAME at the apex. Use an A record for the root and a CNAME for www.

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

Route 53

Route 53 supports apex CNAME flattening via its Alias record type.

  1. Open the Route 53 console and select your hosted zone.
  2. Add an Alias record for the apex:
    • Record name: (leave blank for root)
    • Record type: A
    • Alias: Yes
    • Route traffic to: Alias to another Route 53 record or the value rndrkit.io
  3. Add a CNAME record for www:
    • Record name: www
    • Record type: CNAME
    • Value: rndrkit.io

If you prefer not to use Alias, you can use a plain A record pointing to 35.153.65.36 for the apex.

Vercel DNS

Vercel DNS supports apex CNAME flattening.

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

Verifying DNS Propagation

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

For the www CNAME:

dig www.example.com CNAME +short

The output should show:

rndrkit.io.

For the apex A record:

dig example.com A +short

The output should show:

35.153.65.36

(If you used an apex CNAME / ALIAS on a supported provider, dig example.com CNAME +short will show rndrkit.io. instead.)

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.
  • Apex CNAME on a provider that doesn't support it: GoDaddy, Namecheap, Squarespace Domains, and most registrar DNS cannot put a CNAME at the apex. Use the A record (35.153.65.36) instead.
  • 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