Skip to content

Remove guildbridge CNAME (managed by Worker Custom Domain)#15

Merged
localden merged 1 commit intomainfrom
den/remove-guildbridge-dns
Mar 25, 2026
Merged

Remove guildbridge CNAME (managed by Worker Custom Domain)#15
localden merged 1 commit intomainfrom
den/remove-guildbridge-dns

Conversation

@localden
Copy link
Contributor

Summary

  • Removes the guildbridge CNAME entry from records.ts
  • This subdomain is bound as a Cloudflare Worker Custom Domain, which auto-creates a read-only DNS record not manageable via the DNS API
  • Deploy has been failing since Add guildbridge CNAME pointing to Cloudflare CDN #13 with Cloudflare error 9059 (Invalid CNAME target. Only DNS Only zones can point to partial suffixes)
  • The record stays live — it's managed by the Worker binding, not this Pulumi stack

Test plan

  • CI passes
  • Deploy workflow succeeds on merge (no resources to create/destroy for guildbridge)
  • dig guildbridge.modelcontextprotocol.io still resolves after deploy

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.

:house: Remote-Dev: homespace
@localden localden merged commit 46c093c into main Mar 25, 2026
2 checks passed
@localden localden deleted the den/remove-guildbridge-dns branch March 25, 2026 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant