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

BIND in front of acme-dns #316

Open
SerialDestructor opened this issue Sep 14, 2022 · 1 comment
Open

BIND in front of acme-dns #316

SerialDestructor opened this issue Sep 14, 2022 · 1 comment

Comments

@SerialDestructor
Copy link

SerialDestructor commented Sep 14, 2022

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.

@a-hahn
Copy link

a-hahn commented 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
}

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