[GH-ISSUE #284] NS fallback for queries unrelated to Letsencrypt #147

New issue

Closed

opened 2026-03-13 15:56:25 +03:00 by kerem · 1 comment

kerem commented

2026-03-13 15:56:25 +03:00

Owner

Originally created by @mathroc on GitHub (Oct 25, 2021).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/284

If I understand correctly, all A DNS queries return the same IP, would it be possible to configure acme-dns to fall back to another DNS server for query unrelated to Letsencrypt instead of always answering with the same IP?

I'd like to use that with https://github.com/cunnie/sslip.io/ for local development. I think this would let Traefik (or any Letsencrypt client able to talk with acme-dns) to generate certificate automatically for even for hostname resolving to local addresses

Originally created by @mathroc on GitHub (Oct 25, 2021). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/284 If I understand correctly, all A DNS queries return the same IP, would it be possible to configure acme-dns to fall back to another DNS server for query unrelated to Letsencrypt instead of always answering with the same IP? I'd like to use that with https://github.com/cunnie/sslip.io/ for local development. I think this would let Traefik (or any Letsencrypt client able to talk with acme-dns) to generate certificate automatically for even for hostname resolving to local addresses

kerem closed this issue

2026-03-13 15:56:30 +03:00

kerem commented

2026-03-13 15:56:36 +03:00

Author

Owner

@joohoi commented on GitHub (Jan 25, 2022):

Thanks for sending in the question; It kind of could, but as acme-dns is not designed to serve as an actual DNS server outside of doing ACME DNS validation, I'd hate to encourage people to configure it to do something else. This would also unnecessarily complicate the current codebase.

Closing this issue now, but feel free to comment if something was left unclear and we'll open if a need arises.

@joohoi commented on GitHub (Jan 25, 2022): Thanks for sending in the question; It kind of could, but as acme-dns is not designed to serve as an actual DNS server outside of doing ACME DNS validation, I'd hate to encourage people to configure it to do something else. This would also unnecessarily complicate the current codebase. Closing this issue now, but feel free to comment if something was left unclear and we'll open if a need arises.

kerem referenced this issue

2026-03-13 16:17:41 +03:00

[PR #147] [MERGED] Update vendored dependencies #326