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

Add Resolvers Directive to global module option #4

Open
erroltuparker opened this issue Apr 15, 2024 · 1 comment
Open

Add Resolvers Directive to global module option #4

erroltuparker opened this issue Apr 15, 2024 · 1 comment

Comments

@erroltuparker
Copy link

Hi,

So I've have been troubleshooting this issue for a while and I just managed to solve it.

It appears that resolvers needs to be defined for this to module to work correctly when using your own self-hosted instance for dns.

By utilizing the tls block and adding resolvers to point to the rfc2136 server, everything works correctly. When using the global block, I constantly getting errors that it is waiting for dns, while doing any dns test returns positive (internally and externally).

I decided on the cuff to test adding it to the json block as I had to add resolvers for my cloudflare entry and it appeared that resolvers weren't a global option. Instantly my certificate was issued and working again which is why i'm now using the tls block instead of the global block, but I rather just define it globally.

Thoughts for any reason this is not feasible to action?

@KaiStarkk
Copy link

Agreed, it's a bit cumbersome to add it to each block.

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

No branches or pull requests

2 participants