search

tobychui / zoraxy

A general purpose HTTP reverse proxy and forwarding tool. Now written in Go!
https://zoraxy.aroz.org
GNU Affero General Public License v3.0
3.01k stars 182 forks source link

Dedicated Resolver-IP for DNS-Challenge #319

Open markusglaetzner opened 1 month ago

markusglaetzner commented 1 month ago

for those who internaly host an authoritative DNS server (e.g. Technitium DNS), it is not possible to get the acme process working with dns challange. The only solution is to offer an option to enter a dedicated challenge-dns-resolver-ip for the acme-process. Can you add such an option?

tobychui commented 1 month ago

@yeungalan Can you take a look at this to see if this is feasible with our current implementation using Lego? Thanks!

yeungalan commented 1 month ago

Should be possible, we can take a look if we can implement this

markusglaetzner commented 1 month ago

That would be fantastic! When I should test, please let me know.

Sickjuicy commented 3 weeks ago

Hey i have the same problem if you guys need one more test subject :)

markusglaetzner commented 3 weeks ago

Hi, is there any new status on this topic? If there is something to test, let us know. Thanks.

tobychui commented 2 weeks ago

@markusglaetzner No, but I can help you to ping @yeungalan again with no grantee that there will be new status.

yeungalan commented 2 weeks ago

Hey there! Thanks for your interest in this. We're making steady progress on this feature, but since Zoraxy is something we’re working on alongside our full-time jobs, it's moving along a bit slowly. We’ll keep you posted and let you know as soon as it’s ready. Thanks for hanging in there with us!

swoop124 commented 2 weeks ago

Hello,

i am also intrested in this. For now, i've configured external dns-servers in docker to verify the certs, but now i can't use internal names anymore. So it would be very cool, if this feature is implemented.

thanx

markusglaetzner commented 1 week ago

In the new version (3.1.2) there still isn't an option to put in a separate ip resolver (e.g. 1.1.1.1) for the let's encrypt process. PollingInterrval and Propagation Timeout are nice options, but they do not fix the dns-problem. Are there any news on this issue?

tobychui commented 1 week ago

@markusglaetzner you gonna ask the acme module maintainer for this matter.

For a quick reminder, this is an open source project developed by contributors in their free time. And from my observations, contributors usually only pick up and prioritize working on things they need or interested. If you really need it urgently, you are welcomed for creating a pull request :)

markusglaetzner commented 1 week ago

I was just happy to see that there was an update and since something changed in the Let's Encrypt options, I thought that this option might already be included. Sorry if I came across wrong.