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.

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

Added option to provide custom dns challenge resolvers #251

Open
wants to merge 3 commits into
base: unstable
Choose a base branch
from

Conversation

SamuelNitsche
Copy link

@SamuelNitsche SamuelNitsche commented May 12, 2024

When installing Cosmos Server in internal networks using split dns, letsencrypt dns challenges will most likely fail since the local dns server is used as challenge resolver.

This PR updates the UI and backend to provide an (optional) dns server which is used to resolve the dns challenge.
If the user does not enter a custom server, it will just fall back to the local dns server configured on the machine. Users can also provide multiple servers by separating them using a comma.

Closes #43

Copy link

cla-bot bot commented May 12, 2024

We require contributors to sign our Contributor License Agreement. In order for us to review and merge your code, add yourself to the .clabot file as contributor, as a way of signing the CLA.

Copy link

cla-bot bot commented May 12, 2024

We require contributors to sign our Contributor License Agreement. In order for us to review and merge your code, add yourself to the .clabot file as contributor, as a way of signing the CLA.

@azukaar
Copy link
Owner

azukaar commented Aug 1, 2024

Thanks! (and sorry for the delay reviewing it)
This looks good but shouldnt the input only appear if the DNS Challenge is selected?

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.

2 participants