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
IPv6-only support #88
Comments
Yes, I agree that this may be a problem. My initial thought was to get the standard DNS resolver for the system and use that, but it didn't work out. Making it configurable may be the best option. |
Well, it can be that easy! I did not test it with an actual staging / live challenge, though. (It does not fix the fascist firewall problem, but that is an edge case.) |
I will leave this open to track the "fascist firewall" issue :P |
There is not really something we can do in a broad sense. We will handle the issues if any in relation to this on a case-by-case basis. |
Pending Let's Encrypts's IPv6 support (IPv6-only hosts), I guess bootstrapping off a magic IPv4 DNS forwarder is going to be a problem...
There are systems out there that let only certain DNS forwarders through their firewalls (to mitigate cache poison attacks etc), so maybe it would be an idea to provide a configurable forwarder?
The text was updated successfully, but these errors were encountered: