Remove guildbridge CNAME record (#15)

The guildbridge subdomain is managed by a Cloudflare Worker Custom
Domain binding, which creates a read-only DNS record that cannot be
managed via the DNS API. Attempting to create it via Pulumi fails with
Cloudflare error 9059 ("Invalid CNAME target. Only DNS Only zones can
point to partial suffixes"), blocking all deploys since #13.

The record remains live and functional — it's managed by the Worker
binding, not this stack.

🏠 Remote-Dev: homespace
This commit is contained in:
Den Delimarsky 2026-03-25 15:24:07 -07:00 • committed by GitHub
commit 46c093cee9
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -34,11 +34,8 @@ export const DNS_RECORDS: Record<string, DnsRecordConfig[]> = {
// Other subdomains
{ subdomain: 'example-server', type: 'CNAME', content: 'ghs.googlehosted.com' },
{ subdomain: 'meet', type: 'CNAME', content: 'mcp.meetable.org' },
{
subdomain: 'guildbridge',
type: 'CNAME',
content: 'guildbridge.modelcontextprotocol.io.cdn.cloudflare.net',
},
// guildbridge.modelcontextprotocol.io is managed by a Worker Custom Domain binding
// (read-only record, not manageable via DnsRecord)
// MX record for Google Workspace
{ subdomain: '@', type: 'MX', content: 'smtp.google.com', priority: 1 },