dns-heaven icon indicating copy to clipboard operation
dns-heaven copied to clipboard

kubectl throws error related to Google OAuth when dns-heaven is up

Open missingdays opened this issue 6 years ago • 4 comments

Thanks for creating this tool, it temporarily fixed the problem with kube dns.

But after some time kubectl started to give this error

Unable to connect to the server: failed to refresh token: Post https://oauth2.googleapis.com/token: dial tcp: lookup oauth2.googleapis.com on 127.0.0.1:53: read udp 127.0.0.1:59449->127.0.0.1:53: i/o timeout

when trying to execute any command. e.g.

kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Unable to connect to the server: failed to refresh token: Post https://oauth2.googleapis.com/token: dial tcp: lookup oauth2.googleapis.com on 127.0.0.1:53: read udp 127.0.0.1:59449->127.0.0.1:53: i/o timeout

If I kill the dns-heaven process, kubectl works as before (still giving error related to dns)

kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
The connection to the server ... was refused - did you specify the right host or port?

Restarting the dns-heaven doesn't help, kubectl still throws error about oauth token.

missingdays avatar Jan 17 '19 10:01 missingdays

Found this log in dns-heaven output

ERRO[0005] error resolving query                         error="read udp 192.168.0.65:56801->94.19.255.3:53: i/o timeout" ns="94.19.255.3:53" qname=oauth2.googleapis.com.
ERRO[0005] error resolving query                         error="read udp 192.168.0.65:62111->94.19.255.3:53: i/o timeout" ns="94.19.255.3:53" qname=oauth2.googleapis.com.

missingdays avatar Jan 17 '19 10:01 missingdays

I think the problem is with your DNS server: 94.19.255.3

It may be blocking me (being in Russia and me in the USA) but I get a timeout whenever using that DNS server.

docwhat avatar Mar 22 '19 15:03 docwhat

I have the same trouble but with terraform aws provider. How did you get dns-heaven output?

ipleten avatar Sep 23 '21 17:09 ipleten

How did you get dns-heaven output?

Run as root: # killall dns-heaven; dns-heaven

Diaz-Manuel avatar Mar 07 '23 12:03 Diaz-Manuel