[FeatureRequest] More DNS provider (for the DNS challenge)

[DragoQC]

I would really like to switch to nginx ignition but i'm using porkbun for my dns.
Its not in the list of providers.
Is it planned to add more?

Its already on NPM and im currently using NPM but i think for like hosting multiple minecraft servers i could use ignition.

[lucasdillmann]

Hi @DragoQC,

Yes, I can add the support for Porkbun. The support for it already exists in the library ignition uses to issue certificates, I just haven't exposed it in the UI yet because I don't have an account to validate that it works as expected.

If I generate a development Docker image with Porkbun support enabled, could you help me test if everything works correctly before I enable it on the stable/final image?

[DragoQC]

docker pull dillmann/nginx-ignition:pr-20-snapshot
Am i right?

[lucasdillmann]

Yes, that's the image. Just pull it again (or use --pull always on docker run) because I was making some basic tests here and the image was updated a few times between one test and another, but it's ready now.

If the integration works as expected or you find any problem, please let me know. Thanks for the help.

[DragoQC]

I will test it this Week-End.
My home server is like semi-prod so i cant shut it down whenever i want but i'll let you know :P
Thx a lot for quick answer <3

[lucasdillmann]

No problems. Thanks again for the suggestion and help with testing.

[lucasdillmann]

@DragoQC, over the last few days, I looked into the library that ignition uses for issuing Let's Encrypt certificates and the DNS providers it supports. They seem stable, well-tested, and widely used, so I've decided to enable all of them in ignition.

Version 2.16.0 is now out, supporting all 157 DNS providers, including Porkbun. Please let me know if you run into any problems using the new version.