-
Notifications
You must be signed in to change notification settings - Fork 428
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
Cannot unmarshal DNS message #358
Comments
Hello again @raintonr thanks for reporting this issue. I haven't yet encountered it but that was a good read. It seems to suggest a non compliance given that the UDP DNS response could be greater than 512 bytes yet doesn't cause the |
Well, interestingly I now get:
... so this appears to have 'gone away' on it's own so cannot reproduce it prior to testing the fix. Sorry :( |
Yeah unfortunately this is an issue that maybe if it returns, you can open on the golang issues page as drive has no control over such. |
cannot unmarshal DNS message in heroku...How resolve this problem?? Post https://api.heroku.com/login: dial tcp: lookup api.heroku.com on 127.0.1.1:55: cannot unmarshal DNS message |
Just today I started getting this error on push:
Note the DNS server on my LAN (10.1.109.1) does properly resolve www.googleapis.com:
Note the message size is 518 bytes.
If we try Google's public DNS we get a much shorter reply:
Doing a quick search I find some errors regarding the Go language not being able to handle large DNS replies. See hashicorp/consul#854
I'm logging this here in case anyone else using drive sees similar issue and wants to know how to fix it.
The text was updated successfully, but these errors were encountered: