Unable to run heroku login 'cannot unmarshal DNS message'
#1899
Comments
|
Updated to the latest version, Same result. |
|
Facing the same issue +1 |
|
@mulchy @nitinsurana Sorry for the delayed response, but I have not been able to reproduce this locally. Thank you for the link that you posted, it should help me debug things from your side. Would either of you feel comfortable using tcpdump to analyze things from your side? I ran it locally and could not find any records > 512 which seems to be the underlying issue. Basically open two windows, one running |
|
Could you also check .heroku/error.log to see if there is a backtrack for this? |
|
Here is what I get when running And below is the content of error.log file |
|
@nitinsurana thanks so much for your tcpdump, I updated my dns to 8.8.8.8, but was not able to recreate. Could you please run |
|
It works at my office though. At home wifi, will run the |
|
@ransombriggs I am having the opposite problem of @nitinsurana, and can only reproduce this at work. :) I will check and see if I am still facing the issue tomorrow. If I am understanding the situation correctly, some DNS server (potentially totally unrelated to Heroku) is not following the spec and sending too large of a message? Maybe this is not even really a Heroku cli issue? |
|
@mulchy I was originally thinking the same thing, that it was a misconfigured DNS server outside of our control. But the fact that @nitinsurana is using 8.8.8.8 made me want to investigate this further, as I suspect there is a decently large group of people that use the Google public DNS. As for why I get a different size response from 8.8.8.8, I need to investigate that further, thinking possibly it is a configuration setting. Wanted to get just a little more information before I take this issue to a true DNS expert. |
|
Here is the output of dig command |
|
@ransombriggs I get this (not sure if this is helpful or not) |
|
output of If I am reading this output correctly it looks like the amazon servers are sending responses larger than 512 bytes. output of dig api.heroku.com (very similar to others) |
|
@mulchy @nitinsurana Could you please run the following commands? We recently updated Go from 1.5.3 to 1.6 and I want to make sure that you still have the DNS issue with the updated version of the compiler. |
|
@nitinsurana Could you also run this as well, I noticed that you get a response too large from the Google Public DNS, but the dig example from before went against your local DNS. Being able to use a publicly available DNS server as an example will make debugging easier. Also, what is your exact OS version? |
|
@mulchy @nitinsurana I was doing some more research into the problems you were having when a co-worker pointed me to the following issue golang/go#6464 which indicates that the go dns resolver does not support edns which would explain your problem. I turned off the netgo compilation flag, which we had enabled to try and fix this issue #1886 which I will try and fix in a different manner. Could you please run the following commands to verify you have |
|
After upgrading I still see DNS messages over 512 bytes coming through, but I am able to login successfully. I would recommend closing this issue. output of |
|
Also thanks so much for your help @ransombriggs! |
|
@mulchy thanks for all your debugging help, glad to hear this worked! |
|
After upgrading heroku-toolbelt using |
|
Good to hear! |
Hey,
My heroku version
Result of running
heroku loginI believe this is related to golang 1.5.3 and this issue golang/go#11070
I don't know too much about the DNS spec, but your DNS servers might be sending responses over 512 bytes?
The text was updated successfully, but these errors were encountered: