[GH-ISSUE #5958] FEATURE REQUEST: DNS challenge to allow for letsencrypt wildcard certificates. #12541

Open
opened 2026-08-05 02:06:08 -04:00 by saavagebueno · 2 comments
Owner

Originally created by @J-eremy on GitHub (Apr 21, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5958

Is your feature request related to a problem? Please describe.
An option to use dns challenges instead of the normal ones for single off domains. Right now if you have many sub domains each one is contacting letsencypt individually and tracking renewal time. Most self hosters have one maybe two domains with their services under the,

Describe the solution you'd like
I would like to see an added feature to use the dns challenge so you can get *.domain.com or *.proxy.domain.com in a tidy manner.

Describe alternatives you've considered
Before moving over to netbird I was using traefik, which already has the ability to do this, and traefik is also the reverse proxy in front of netbird in my setup. I still am using traefik internally and they are issuing wildcard certs already.

Additional context
From looking at how it works, the reverse proxy uses its own certificate storage than the traefik instance ahead of it. It sits on its own. It also stores the certs differently from traefik, traefik uses json. Seems to me unifying these two things and taking advantage of the traefik ability to get wildcard certs issued is a no brainer.

Originally created by @J-eremy on GitHub (Apr 21, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5958 **Is your feature request related to a problem? Please describe.** An option to use dns challenges instead of the normal ones for single off domains. Right now if you have many sub domains each one is contacting letsencypt individually and tracking renewal time. Most self hosters have one maybe two domains with their services under the, **Describe the solution you'd like** I would like to see an added feature to use the dns challenge so you can get *.domain.com or *.proxy.domain.com in a tidy manner. **Describe alternatives you've considered** Before moving over to netbird I was using traefik, which already has the ability to do this, and traefik is also the reverse proxy in front of netbird in my setup. I still am using traefik internally and they are issuing wildcard certs already. **Additional context** From looking at how it works, the reverse proxy uses its own certificate storage than the traefik instance ahead of it. It sits on its own. It also stores the certs differently from traefik, traefik uses json. Seems to me unifying these two things and taking advantage of the traefik ability to get wildcard certs issued is a no brainer.
saavagebueno added the feature-request label 2026-08-05 02:06:08 -04:00
Author
Owner

@heymoe commented on GitHub (Apr 30, 2026):

Check this thread out as it might have an unofficial solution for you in it: https://github.com/netbirdio/netbird/issues/5450

<!-- gh-comment-id:4350111466 --> @heymoe commented on GitHub (Apr 30, 2026): Check this thread out as it might have an unofficial solution for you in it: https://github.com/netbirdio/netbird/issues/5450
Author
Owner

@jeliasson commented on GitHub (Jul 7, 2026):

Close as dup?

<!-- gh-comment-id:4903360601 --> @jeliasson commented on GitHub (Jul 7, 2026): Close as dup?
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#12541