Skip to content

Commit 6bb4728

Browse files
authored
Merge pull request #2902 from appwrite/clarify-cname-flattening-proxy-note
Clarify Cloudflare proxy requirement in CNAME flattening blog
2 parents 1c314c5 + 17aedcf commit 6bb4728

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

src/routes/blog/post/announcing-cname-flattening/+page.markdoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,15 @@ category: announcement
1010
featured: false
1111
---
1212

13-
If you've connected a custom domain to Appwrite Sites, you know the process required changing your nameservers to Appwrite. For developers already managing DNS through Cloudflare or similar providers, that meant giving up control over caching, security, email routing, and other configurations just to connect a single site.
13+
If you've connected a custom domain to Appwrite Sites, you know the process required changing your nameservers to Appwrite. For developers already managing DNS through Cloudflare or similar providers, that meant moving email routing, DNS-layer protections, and every other record off their existing provider just to connect a single site.
1414

1515
Appwrite Sites now supports **CNAME flattening**, so you can connect your domain by adding a DNS record with your existing provider instead of migrating nameservers.
1616

1717
# Add a record, not a migration
1818

1919
With CNAME flattening support, connecting a custom domain is just a DNS record away. Keep your existing provider, add a CNAME or ALIAS/ANAME record pointing to Appwrite, and verify the domain in the Console. Once DNS propagates, your site is live with SSL automatically configured. DNS propagation can take anywhere from a few minutes to a few hours depending on your provider and TTL settings.
2020

21-
This is especially useful for teams that rely on their DNS provider for more than just domain resolution. If Cloudflare handles your caching, security headers, or MX records, you no longer have to choose between that setup and Appwrite Sites.
21+
This is especially useful for teams that rely on their DNS provider for more than just domain resolution. You keep DNS-level configuration like MX records and DNS-layer protections with your existing provider, while Appwrite serves your site through its own CDN with SSL, caching, and edge security built in. If you use Cloudflare, set the record to **DNS only** (grey cloud, not the orange proxy) so traffic reaches Appwrite's CDN directly.
2222

2323
# How CNAME flattening works
2424

@@ -31,7 +31,7 @@ Depending on your provider, this goes by different names. Cloudflare calls it **
3131
1. Open your site's domains tab in the Appwrite Console.
3232
2. Add your custom domain.
3333
3. Appwrite provides a CNAME record details.
34-
4. Go to your DNS provider and create a DNS record as described by Appwrite. Providers like Cloudflare will handle CNAME flattening at the root automatically. On other providers, you may need to use an ALIAS or ANAME record for the root domain.
34+
4. Go to your DNS provider and create a DNS record as described by Appwrite. Providers like Cloudflare will handle CNAME flattening at the root automatically. Just make sure the record is set to **DNS only** (grey cloud), not proxied. On other providers, you may need to use an ALIAS or ANAME record for the root domain.
3535
5. Return to Appwrite and verify the domain.
3636

3737
# Available now

0 commit comments

Comments
 (0)