Support for provider: Knot (self-hosted)

[McSinyx]

Welcome

• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, the DNS provider exposes a public API.
• Yes, I know that the lego maintainers don't have an account in all DNS providers in the world.
• Yes, I'm able to create a pull request and be able to maintain the implementation.
• Yes, I'm able to test an implementation if someone creates a pull request to add the support of this DNS provider.

How do you use lego?

Other

Link to the DNS provider

https://www.knot-dns.cz

Link to the API documentation

https://www.knot-dns.cz/docs/latest/html/man_knsupdate.html

Additional Notes

I use NixOS security.acme.certs for automated renewal.

Support for Knot has been implemented for acme.sh. I may be able to implement it for Lego with some guidance.

[ldez]

Hello,

to create an implementation you can follow this implementation: https://github.com/go-acme/lego/tree/master/providers/dns/njalla

You can ask me questions if you need.

[ldez]

@McSinyx any news?

[Saklad5]

Why not use RFC 2136? That's what I use.

---

I would appreciate the ability to use Unix domain sockets with RFC 2136, which Knot DNS added support for in 3.2.5.

[McSinyx]

Thanks, I thought about using exec but RFC 2136 is much better.

[Saklad5]

I've opened a distinct issue for the UDS request.