[GH-ISSUE #237] Bug: Duplicated entries in txt database on registration #115

New issue

Open

opened 2026-03-13 15:48:37 +03:00 by kerem · 3 comments

kerem commented

2026-03-13 15:48:37 +03:00

Owner

Originally created by @MyIgel on GitHub (Aug 10, 2020).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/237

Somehow the current docker hub version creates two rows in the txt table when registering a new api user which can both contain different values and that leads to two returned txt records which seems to confuse some programs.

Originally created by @MyIgel on GitHub (Aug 10, 2020). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/237 Somehow the current docker hub version creates two rows in the txt table when registering a new api user which can both contain different values and that leads to two returned txt records which seems to confuse some programs.

kerem commented

2026-03-13 15:48:43 +03:00

Author

Owner

@webprofusion-chrisc commented on GitHub (Aug 20, 2020):

When you request a wildcard and a primary domain (e.g. *.example.com and example.com) the app creates 2 TXT record values on purpose so that validation will pass for either variant. Is this what you mean?

@webprofusion-chrisc commented on GitHub (Aug 20, 2020): When you request a wildcard and a primary domain (e.g. `*.example.com` and `example.com`) the app creates 2 TXT record values on purpose so that validation will pass for either variant. Is this what you mean?

kerem commented

2026-03-13 15:48:48 +03:00

Author

Owner

@MyIgel commented on GitHub (Oct 26, 2020):

I mean that when changing the certificate (for example to add another domain) only one of the records gets updated

b09f887a-9579-4989-a0f5-e02bfa7e1968|Ailm7VzUNU1BZH6QHgqCDJM3yqN_8ILu4r_kyF8YaZw|1603721005
b09f887a-9579-4989-a0f5-e02bfa7e1968|r8DDPpuHjv424EXGNht_iD3QV_kEDeqSLn1Fm4ipTMo|1603721683

which causes validation errors (in cert manager here)

@MyIgel commented on GitHub (Oct 26, 2020): I mean that when changing the certificate (for example to add another domain) only one of the records gets updated ``` b09f887a-9579-4989-a0f5-e02bfa7e1968|Ailm7VzUNU1BZH6QHgqCDJM3yqN_8ILu4r_kyF8YaZw|1603721005 b09f887a-9579-4989-a0f5-e02bfa7e1968|r8DDPpuHjv424EXGNht_iD3QV_kEDeqSLn1Fm4ipTMo|1603721683 ``` which causes validation errors (in cert manager here)

kerem commented

2026-03-13 15:48:53 +03:00

Author

Owner

@webprofusion-chrisc commented on GitHub (Oct 27, 2020):

Your app (cert manager) needs to pass the Let's Encrypt validation request details to acme-dns for each domain entry. So if your cert has 4 domains or subdomains that's 4 updates to acme-dns for 4 different records before the cert request can complete validation. I'd check with the cert-manager folks to ensure their acme-dns support is behaving.

@webprofusion-chrisc commented on GitHub (Oct 27, 2020): Your app (cert manager) needs to pass the Let's Encrypt validation request details to acme-dns for each domain entry. So if your cert has 4 domains or subdomains that's 4 updates to acme-dns for 4 different records before the cert request can complete validation. I'd check with the cert-manager folks to ensure their acme-dns support is behaving.