Skip to content
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.

Sign up for GitHub

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

Update custom-dns.md #8399

Merged
merged 2 commits into from
Jan 31, 2025
Merged

Update custom-dns.md #8399

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
626edec
Update custom-dns.md
josh-konghq Jan 31, 2025
5b88cf0
Apply suggestions from code review
cloudjumpercat Jan 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions app/konnect/gateway-manager/dedicated-cloud-gateways/custom-dns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,3 +37,17 @@ title: Custom Domains for Dedicated Cloud Gateways
1. In {{site.konnect_short_name}}, open {% konnect_icon runtimes %} **Gateway Manager**, choose a control plane to open the **Overview** dashboard, then click **Custom Domains**.

2. Click the action menu on the end of the row you want to delete and click **Delete**.

## Custom Domain Attachment & CAA Record Issue
cloudjumpercat marked this conversation as resolved.
Show resolved Hide resolved

If your custom domain attachment fails, check if your domain has a CAA record restricting certificate issuance. Dedicated Cloud Gateways uses GCP Public CA to provision SSL/TLS certificates. If your CAA record does not include the required CA, certificate issuance will fail.
cloudjumpercat marked this conversation as resolved.
Show resolved Hide resolved

Steps to Fix:
cloudjumpercat marked this conversation as resolved.
Show resolved Hide resolved
1. Check existing CAA records
* Run: dig CAA yourdomain.com +short
* If a CAA record exists but doesn't allow GCP Public CA (pki.goog), update it.
cloudjumpercat marked this conversation as resolved.
Show resolved Hide resolved
2. Update the CAA record (if needed)
* yourdomain.com. CAA 0 issue "pki.goog"
cloudjumpercat marked this conversation as resolved.
Show resolved Hide resolved
3. Wait for DNS propagation and retry attaching your domain.

If no CAA record exists, no changes are needed. More details: [Let's Encrypt CAA Guide](https://letsencrypt.org/docs/caa/)
cloudjumpercat marked this conversation as resolved.
Show resolved Hide resolved
Loading