-
Notifications
You must be signed in to change notification settings - Fork 228
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
BIND in front of acme-dns #316
Comments
Only one ip available same situation here. I'm using coreDNS as a forwarder for acme-dns. Both in docker containers. It did not work when both containers were located on the same host due to udp issues with docker. In coreDNS you can enforce forwarding to tcp. This solved my problem
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is it possible to set BIND up as a slave / forwarder for acme-dns? I tried it both using a slave and a forward configuration, but they didn't work: (either REFUSED (forward) or SERVFAIL (slave).
I have tried these configurations:
I want to use BIND for dynamic dns updates and I have only one IP available.
The text was updated successfully, but these errors were encountered: