Custom domain of status page can't be verified if it's a apex domain #17

Open
opened 2026-04-05 16:18:41 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @BluemediaDev on 3/24/2026

Describe the bug
In response to #2138, the possibility to add apex domains as custom domains to status pages was introduced. However, it's currently impossible to verify apex domains, as OneUptime expects a CNAME record that isn't allowed at the apex level.

To Reproduce
Steps to reproduce the behavior:

  1. Add apex domain as custom domain to a status page
  2. Create A/AAAA record pointing to OneUptime (as CNAMEs aren't allowed)
  3. Try to verify the CNAME for the custom domain

Expected behavior
There should be a way to verify apex domains for status pages.

Desktop

  • OS: Fedora 43
  • Browser: Firefox 148.0.2

Deployment Type
Self hosted
OneUptime version: 10.0.37

*Originally created by @BluemediaDev on 3/24/2026* **Describe the bug** In response to #2138, the possibility to add apex domains as custom domains to status pages was introduced. However, it's currently impossible to verify apex domains, as OneUptime expects a CNAME record that isn't allowed at the apex level. **To Reproduce** Steps to reproduce the behavior: 1. Add apex domain as custom domain to a status page 2. Create A/AAAA record pointing to OneUptime (as CNAMEs aren't allowed) 3. Try to verify the CNAME for the custom domain **Expected behavior** There should be a way to verify apex domains for status pages. **Desktop** - OS: Fedora 43 - Browser: Firefox 148.0.2 **Deployment Type** Self hosted OneUptime version: 10.0.37
MrUnknownDE added the bugbugbugbug labels 2026-04-05 16:18:42 +02:00
Sign in to join this conversation.
No Label bug bug bug bug
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#17