[GH-ISSUE #26] Host to delete entries in the db #18

Closed
opened 2026-03-13 16:26:50 +03:00 by kerem · 1 comment
Owner

Originally created by @SamCN2 on GitHub (Apr 8, 2025).
Original GitHub issue: https://github.com/acme-dns/acme-dns-client/issues/26

Hi,

I had forgotten how to use, and I registered a record that defaulted to auth.acme-dns.io instead of my own server domain.
So, all of the prompts from certbot point to acme-dns.io.

How to remove or replace the entries. I have tried to re-register with the proper domain.

That is:

I first did:
$ sudo acme-dns-client register -d my.dom.ain

I should have done:
$ sudo acme-dns-client register -d my.dom.ain -s acme.dom.ain

And now I can't get the default auth.acme-dns.io out of my database.

And running the proper command doesn't seem to repair the mistake.

The entries are hashed, at that...so I can't manually delete them.
(An aside, do the hases match the DNS CNAME entries, I could go for those blindly, I suppose)

Thanks!

Originally created by @SamCN2 on GitHub (Apr 8, 2025). Original GitHub issue: https://github.com/acme-dns/acme-dns-client/issues/26 Hi, I had forgotten how to use, and I registered a record that defaulted to auth.acme-dns.io instead of my own server domain. So, all of the prompts from certbot point to acme-dns.io. How to remove or replace the entries. I have tried to re-register with the proper domain. That is: I first did: $ sudo acme-dns-client register -d my.dom.ain I should have done: $ sudo acme-dns-client register -d my.dom.ain -s acme.dom.ain And now I can't get the default auth.acme-dns.io out of my database. And running the proper command doesn't seem to repair the mistake. The entries are hashed, at that...so I can't manually delete them. (An aside, do the hases match the DNS CNAME entries, I could go for those blindly, I suppose) Thanks!
kerem closed this issue 2026-03-13 16:26:55 +03:00
Author
Owner

@SamCN2 commented on GitHub (Apr 9, 2025):

So, I think I know enough to start over without loosing too much. After pouring through the code it became clear that 1) I should have done this when moving from the python to this go program and 2) this program dangerously set the default server to auth.acme-dns.io. As there is no easy way to undo things, please don't set a default that defeats the purpose of running my own server. We're human out here, and we forget to complete command lines from time to time.

<!-- gh-comment-id:2790968734 --> @SamCN2 commented on GitHub (Apr 9, 2025): So, I think I know enough to start over without loosing too much. After pouring through the code it became clear that 1) I should have done this when moving from the python to this go program and 2) this program dangerously set the default server to auth.acme-dns.io. As there is no easy way to undo things, please don't set a default that defeats the purpose of running my own server. We're human out here, and we forget to complete command lines from time to time.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/acme-dns-client#18
No description provided.