Skip to content
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

DNS failure in corporate environments #8

Open
mikebryant opened this issue Oct 3, 2016 · 4 comments
Open

DNS failure in corporate environments #8

mikebryant opened this issue Oct 3, 2016 · 4 comments

Comments

@mikebryant
Copy link

In our environment we have no direct access to 8.8.8.8, 8.8.4.4 which are the defaults used by lego, instead of the ones provided by the OS/Kubernetes

We've got a PR open upstream at go-acme/lego#293 - I'm opening this to track this issue, once it's merged we'd like a new build of kube-cert-manager to incorporate the fix, if possible? :)

@luna-duclos
Copy link

That's totally fine! :) If you can let me know when the PR is merged, I'll make a new build

@stuart-warren
Copy link

ping @mikebryant that PR was merged, though no releases since April

@druidsbane
Copy link

ping @PSG-Luna @mikebryant as this was merged a while ago, any chance we can get a new build that includes this?

@druidsbane
Copy link

@luna-duclos @mikebryant any chance we can get this released or add a flag: -dns-resolvers to match the functionality of lego itself so we can override the default DNS resolvers?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants