-
Notifications
You must be signed in to change notification settings - Fork 307
Add cname flattening announcement #2785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
2cd3666
Add cname flattening announcement
atharvadeosthale f43fac7
add cover
atharvadeosthale 9d66cc1
add changelog
atharvadeosthale 990d242
update cover again
atharvadeosthale d58ab89
comments
atharvadeosthale 2cd95cc
Apply suggestions from code review
atharvadeosthale File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
47 changes: 47 additions & 0 deletions
47
src/routes/blog/post/announcing-cname-flattening/+page.markdoc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| --- | ||
| layout: post | ||
| title: "Announcing CNAME flattening support: Connect your domain without changing nameservers" | ||
| description: Appwrite Sites now supports CNAME flattening, so you can connect custom domains by adding a DNS record with your existing provider instead of migrating nameservers. | ||
| date: 2026-03-06 | ||
| cover: /images/blog/announcing-cname-flattening/cover.png | ||
| timeToRead: 4 | ||
| author: matej-baco | ||
| category: announcement | ||
| featured: false | ||
| --- | ||
|
|
||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
| # Add a record, not a migration | ||
|
|
||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
| # How CNAME flattening works | ||
|
|
||
| Standard DNS rules don't allow CNAME records at the root domain (`example.com`). Only subdomains (`www.example.com`) can use CNAME. CNAME flattening works around this: your DNS provider accepts a CNAME-like configuration at the root, resolves the target internally, and returns the corresponding IP addresses to the client. | ||
|
|
||
| Depending on your provider, this goes by different names. Cloudflare calls it **CNAME flattening**, Route 53 uses **ALIAS records**, and some providers support **ANAME records**. The implementation varies, but the result is the same: your root domain can point to a hostname without breaking DNS standards. | ||
|
|
||
| # Connect your domain | ||
|
|
||
| 1. Open your site's domains tab in the Appwrite Console. | ||
| 2. Add your custom domain. | ||
| 3. Appwrite provides a CNAME record details. | ||
| 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. | ||
| 5. Return to Appwrite and verify the domain. | ||
|
|
||
| # Available now | ||
|
|
||
| CNAME flattening support is available today on **Appwrite Cloud**. Head to your site dashboard, add a custom domain, and follow the updated DNS instructions. | ||
|
|
||
| As always, we'd love to hear your feedback. If you run into any issues, join the [Appwrite community](https://appwrite.io/discord) and let us know. | ||
|
|
||
| # More resources | ||
|
|
||
| - [Read the custom domains documentation](/docs/products/sites/domains) | ||
| - [Learn about Appwrite DNS](/docs/products/network/dns) | ||
| - [Set up a custom domain for your Appwrite project](/docs/advanced/platform/custom-domains) | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| layout: changelog | ||
| title: "CNAME flattening support for Appwrite Sites" | ||
| date: 2026-03-06 | ||
| cover: /images/blog/announcing-cname-flattening/cover.png | ||
| --- | ||
|
|
||
| You can now connect a custom domain to Appwrite Sites without changing your nameservers. Appwrite Sites now supports CNAME flattening and similar apex-domain features provided by modern DNS providers. | ||
|
|
||
| Instead of migrating nameservers to Appwrite, you can add a DNS record with your existing provider, verify the domain in the Console, and go live. This works with CNAME flattening (Cloudflare), ALIAS records (Route 53), and ANAME records, depending on your provider. | ||
|
|
||
| {% arrow_link href="/blog/post/announcing-cname-flattening" %} | ||
| Read the announcement | ||
| {% /arrow_link %} |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add the required
draftandlastUpdatedfrontmatter.src/routes/blog/content.tstreats both fields as required and reads them for every post. Leaving them out here will produce incomplete post metadata (draft: undefined,lastUpdated: Invalid Date) in the generated blog index.🛠️ Minimal fix
📝 Committable suggestion
🤖 Prompt for AI Agents