DNS proxy

The three records

The wizard (Domains → Add domain → DNS proxy) shows the exact name and value for each record with a copy button. The values are unique to your domain — copy them from the wizard rather than typing from this page.

Timing

DNS changes usually take effect in 5–15 minutes, but can take up to 24 hours to propagate fully. SSL validation also typically completes 5–15 minutes after the records resolve. If verification fails, wait a few minutes and try again — nothing is lost by retrying.

Cloudflare Quick Connect

When you add a domain, Wrenda detects the DNS provider from the nameservers. If the domain is in a Cloudflare account you have connected, the wizard offers Quick Connect instead of manual records. Clicking it will:

1. Add the CNAME record pointing to proxy.wrenda.ai, set to DNS only.
2. Activate the worker route for your domain.
3. Verify the domain automatically.

You can still open Cloudflare's DNS settings from the wizard and configure the records manually if you prefer.

Verify

1. Add the records at your DNS provider

   Provider-specific steps are below.

2. Click Verify DNS Records

   The per-record checklist shows Found / Not found for the CNAME, the DCV CNAME and the ownership TXT, plus the SSL certificate status.

3. Check from the command line (optional)

   bashCopy

   # CNAME resolves to Wrenda
   dig +short CNAME your-domain.com
   # → proxy.wrenda.ai.
   
   # Headers show Wrenda in the path
   curl -I -H "User-Agent: GPTBot/1.0" "https://your-domain.com/"

Per-provider instructions

Menus move around; these are the current paths as far as we know. The record contents are always the same three rows from the wizard.

Cloudflare

1. Prefer Quick Connect if it is offered.
2. Otherwise open Websites → your zone → DNS → Records.
3. Delete any existing A, AAAA or CNAME for the name you are pointing at Wrenda.
4. Add each record. For the two CNAMEs, click the orange cloud so it turns grey (DNS only).
5. If your origin was also on this zone (orange-clouded), leave its own record alone — Wrenda fetches the origin by the URL you gave in the wizard, not by the domain.

GoDaddy

1. My Products → Domains → DNS (Manage DNS).
2. Delete the parked A record for @ if you are pointing the apex domain at Wrenda.
3. Add New Record for each row. Use @ for the apex, www for the www host.

Namecheap

1. Domain List → Manage → Advanced DNS.
2. Remove the default URL Redirect / A records for the host you are changing.
3. Add New Record: for the apex choose type ALIAS (if offered) or use www with a CNAME; Host @ or www; Value proxy.wrenda.ai.
4. Add the _acme-challenge CNAME and the TXT record with the Host set to the part of the name before your domain (Namecheap appends the domain automatically).

Amazon Route 53

1. Hosted zones → your zone → Create record.
2. Delete existing A / AAAA / Alias records for the name first.
3. Create the CNAME with Record name www (or blank for the apex where allowed), Record type CNAME, Value proxy.wrenda.ai.
4. Create the _acme-challenge CNAME and the TXT record the same way. For TXT, wrap the value in double quotes.

Google Domains / Squarespace

1. Google Domains moved to Squarespace. Open Domains → your domain → DNS → Custom records.
2. Delete Squarespace's default records for the host you are changing.
3. Add the three records. Host www (or @ if the apex CNAME is accepted), Type, Data.

Any other provider

Find

The DNS / Zone / Advanced DNS editor for the domain (not the registrar’s nameserver settings).

Remove

Existing A, AAAA and CNAME records at the name you are changing.

Add

The three records from the wizard exactly as shown. Leave TTL at the default.

Avoid

Proxy / acceleration toggles on the records; URL-forwarding records; adding a TXT for _acme-challenge.

Then

Return to the wizard and click Verify DNS Records.

www and apex

Add each hostname you want Wrenda to serve as its own domain in the dashboard (for example example.com and www.example.com), each with its own records; the wizard computes the validation names relative to the apex. If your site redirects one to the other, keep that redirect on your origin — Wrenda passes it through.

Next