[GH-ISSUE #361] NOT AN ISSUE! is it possible to split the services on two servers? (one server for HTTPS and another for DNS) #204

New issue

Open

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

kerem commented

2026-03-13 16:08:34 +03:00

Owner

Originally created by @okorsky on GitHub (Sep 4, 2024).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/361

This is not an issue, it's more like a feature question.

is it possible to split the DNS and HTTPS services on two servers? where both will point to the same DB?

Is there a recommended configuration for that setup?

I'm thinking that if I setup 2 servers pointing to the same PostgreSQL database then it should work. But not sure if that's the case.

Originally created by @okorsky on GitHub (Sep 4, 2024). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/361 This is not an issue, it's more like a feature question. is it possible to split the DNS and HTTPS services on two servers? where both will point to the same DB? Is there a recommended configuration for that setup? I'm thinking that if I setup 2 servers pointing to the same PostgreSQL database then it should work. But not sure if that's the case.

kerem commented

2026-03-13 16:08:39 +03:00

Author

Owner

@maddes-b commented on GitHub (Sep 21, 2024):

Having API and DNS on two different machines is not intended, you may try with sharing the DB file from the API machine (does DB updates: /register and /update) to the DNS machine (read only).

Otherwise if the API and DNS are on the same machine, you can serve the API under a different domain by binding API to a local IP (127.0.0.1, ::1, or similar) and use a reverse proxy (e.g. nginx) to accept requests and forward to the API's IP and port.
See https://github.com/joohoi/acme-dns/pull/363 for related information.

@maddes-b commented on GitHub (Sep 21, 2024): Having API and DNS on two different machines is not intended, you may try with sharing the DB file from the API machine (does DB updates: /register and /update) to the DNS machine (read only). Otherwise if the API and DNS are on the same machine, you can serve the API under a different domain by binding API to a local IP (127.0.0.1, ::1, or similar) and use a reverse proxy (e.g. nginx) to accept requests and forward to the API's IP and port. See https://github.com/joohoi/acme-dns/pull/363 for related information.