You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: