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
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:
zone "acme.example.com" in {
type slave;
masters { 192.168.0.10; };
file "/var/cache/bind/db.acme.example.com";
};
zone "acme.example.com" in {
type forward;
forward only;
forwarders { 192.168.0.10; };
};
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:
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
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: