You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this configuration acmetool fails however when the container is set with --dns=8.8.8.8 which forces resolv.conf to a single name server entry:
nameserver 8.8.8.8
it works just fine.
I guess the issue is due to how go library treats any failure of any local DNS server and incorrectly reports it as a total fail to resolve DNS name with the last nameserver in the list. Totally misleading.
For time being we are using --dns flag for acmetool container as a quick fix, but planning to try to recompile acmetool with GO 1.7.1, hopefully it will fix the issue.
Cheers
The text was updated successfully, but these errors were encountered:
[acmetool]
Just finished debuting a weird acmetool behaviour that was causing reconcile task to fail with the following error messages:
error satisfying Target(devops.xxx.xxx;https://acme-v01.api.letsencrypt.org/directory;0): Get https://acme-v01.api.letsencrypt.org/directory: dial tcp: lookup acme-v01.api.letsencrypt.org on 8.8.8.8:53: dial udp 8.8.8.8:53: i/o timeout
I believe the issue is related to golang/go#17329 and it seems that it has been resolved in GO 1.7.1
In our environment acmetool is running in a docker container and by default resolv.conf in the container is based on the host resolv.conf:
With this configuration acmetool fails however when the container is set with --dns=8.8.8.8 which forces resolv.conf to a single name server entry:
nameserver 8.8.8.8
it works just fine.
I guess the issue is due to how go library treats any failure of any local DNS server and incorrectly reports it as a total fail to resolve DNS name with the last nameserver in the list. Totally misleading.
For time being we are using --dns flag for acmetool container as a quick fix, but planning to try to recompile acmetool with GO 1.7.1, hopefully it will fix the issue.
Cheers
The text was updated successfully, but these errors were encountered: