@Tealk Added at the top!
Stay secure,
Peter
@Tealk Added at the top!
Stay secure,
Peter
Missing fom the list:
It has three known bugs right now; two that cause rate-limiting problems, one that causes faulty TXT records.
Hi @sshine,
Welcome to deSEC, and thanks for this suggestion! ![]()
Can you let us know when these known bugs are fixed? It will be nicer when folks don’t immediately run into issues when using a tool from the list. Thanks!
Stay secure,
Peter
I have an addition for the list, as I have added deSEC support to the dns-update Rust library ![]()
Hi @Tyr3al,
Thanks for the suggestion, I’ve added it at the top! And welcome to desEC. ![]()
Stay secure,
Peter
Certainly. I’m afraid it will be a little while, I’ve encountered two more bugs; one more with TXT records, one with incorrect truncation when the record is directly on the apex domain. I’ve written to Michelangelo and asked if he wants a co-maintainer, but otherwise I’m going to highlight my fork as being a little ahead of his.
Hi,
Nginx Proxy Manager and Stalwartlabs/Stalwart (self-hosted mail server) support deSEC.
I have fixed a number of bugs; the fixes live on my fork:
It has a release called ghcr.io/sshine/external-dns-desec-provider:v0.3.5.
But better yet, I have remade the external-dns webhook in Rust with much better rate-limit support:
I’ll make a proper announcement once it has been deployed for a while.