Check multiple nameservers for self check validation if self check status not 200 #6707
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Is your feature request related to a problem? Please describe.
I have different records for domain.com in public and internal DNS server, I can define them both with:
--acme-http01-solver-nameservers="10.1.1.1:53,8.8.8.8:53,"
If status of self check gives 5xx/4xx code on private IP, I would like that self check will also be performed checking 2nd IP defined in 2nd nameserver without a delay.
Now as I understand it only query first DNS server. And if IP is resolved that only checking challenge using that IP.
Describe the solution you'd like
check first DNS in http challenge not only for resolution of IP but also for self check status. If it is not 200, perform check with 2nd DNS immediately.
Or another flag can be set for additional not default DNS, like:
--acme-http01-solver-add-nameservers=
So if flag is defined, do a retry of self check using add-nameservers.
/kind feature
The text was updated successfully, but these errors were encountered: