[GH-ISSUE #316] BIND in front of acme-dns #171

New issue

Open

opened 2026-03-13 16:02:13 +03:00 by kerem · 1 comment

kerem commented

2026-03-13 16:02:13 +03:00

Owner

Originally created by @SerialDestructor on GitHub (Sep 14, 2022).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/316

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.

Originally created by @SerialDestructor on GitHub (Sep 14, 2022). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/316 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.

kerem commented

2026-03-13 16:02:19 +03:00

Author

Owner

@a-hahn commented on GitHub (Sep 15, 2022):

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

acme.example.com:53 {
    forward . 192.168.0.10:5353 {
        force_tcp
    }
    log
    errors
}

@a-hahn commented on GitHub (Sep 15, 2022): 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 ``` acme.example.com:53 { forward . 192.168.0.10:5353 { force_tcp } log errors } ```