-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix DNS local challenge to use the nameserver of the zone #41
Comments
Hi Robbin, Thanks for sharing your suggestion. I see the problem you’re facing, and I’m definitely open to change the way of checking DNS locally. Personally I prefer the https://github.com/spatie/dns package. I worked with it before and I really like their packages. Would that work for you? Unfortunately, I’m quite busy in the upcoming week(s). However, I’ll try to find some time to implement this. |
Didn't know that one, looks good (and love spatie)! No worries, i'll see if I can wrap up a PR soon with a rewrite of the |
@RogierW Never mind, I can work around by requesting the SOA record first :-) |
@RogierW can you reopen this issue? I've stumbled upon a problem. We use When we use When we use |
I'm currently testing this implementation: https://github.com/exonet/rw-acme-client/blob/nameserver-check/src/Support/LocalChallengeTest.php#L36-L54 (It's not ready for a PR yet as this is on the PHP 8.1 branch). Basically:
|
Hi,
I was wondering if you were open for a change to validate DNS locally.
Currently the code uses
dns_get_record
, the problem however is once this is triggered and the record does not exist, it can take quite a while before it is picked up again. My preference would be to use for exampledig
or another way to check the DNS locally.I would like to change the code that the _acme-challenge.zone-name.com is checked agains the nameservers used by zone-name.com. Then use the
dig
command to get the data for the TXT records. An example of an existing package we can use is: https://github.com/bluelibraries/dnsThe text was updated successfully, but these errors were encountered: