DNS lookup issue #121
Comments
|
@andyweiss1982: We have external monitoring tools that haven't picked up these type of issues, but sorry for the trouble! Can you provide more details so we can try to get to the bottom of this? Can you tell us what DNS servers you're using and what location (country or US state) you're trying to make these connections from? |
|
Thank you for the quick response! Currently I am just making these requests from a development environment, I haven’t tried anywhere in production yet.
However, I am located in Miami, FL.
Any guidance you can provide is much appreciated!
… On May 30, 2019, at 4:12 PM, Nick Muerdter ***@***.***> wrote:
@andyweiss1982 <https://github.com/andyweiss1982>: We have external monitoring tools that haven't picked up these type of issues, but sorry for the trouble! Can you provide more details so we can try to get to the bottom of this? Can you tell us what DNS servers you're using and what location (country or US state) you're trying to make these connections from?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#121?email_source=notifications&email_token=AB55PIRRINCUKMQLVV2VVRLPYAYMNA5CNFSM4HRGQSM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWTMNDA#issuecomment-497469068>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB55PIRUVH4SUYPYNRN7D3LPYAYMNANCNFSM4HRGQSMQ>.
|
|
Can you share the DNS servers your development environment is using? On Windows, Mac, or Linux, I think you should be able to determine this by running |
|
Sure thing, is this helpful?
… On May 31, 2019, at 10:10 AM, Nick Muerdter ***@***.***> wrote:
Can you share the DNS servers your development environment is using? On Windows, Mac, or Linux, I think you should be able to determine this by running nslookup developer.nrel.gov on the command line and sharing the output of that. If you're using a local DNS server, then it may also be helpful to find what external DNS servers you're using are. You can discover those by visiting https://browserleaks.com/ip <https://browserleaks.com/ip> and reporting the IP addresses under "Your DNS Servers." Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#121?email_source=notifications&email_token=AB55PIW7BDCX7I4CS26AWTDPYEWV5A5CNFSM4HRGQSM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWVKKFA#issuecomment-497722644>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB55PIRZV4BK5ZVEXT3SGP3PYEWV5ANCNFSM4HRGQSMQ>.
|
|
@andyweiss1982: Hm, I'm not seeing any details in your last message. Was there supposed to be a screenshot, or something else? If you were trying to attach a screenshot, you may need to post that directly to the GitHub interface (#121), rather than attaching it to an e-mail response. |
|
Thanks for the heads up! Screenshots below:
|
I am having trouble connecting to this API. About 40% of the time, it works just fine (I am making a post request with a long linestring, url encoded).
But about 60% of the time, I get this error when making the exact same request:
(getaddrinfo: nodename nor servname provided, or not known (developer.nrel.gov:443))
I have tried from several different wifi networks in different locations and it doesn't appear to be related to any firewall restrictions on my end -- the results are consistently spotty across locations.
Any advice on how I can get a consistent response from the API?
Sanitized, truncated request log below...
I, [2019-05-30T12:12:22.881589 #96234] INFO -- request: POST https://developer.nrel.gov/api/alt-fuel-stations/v1/nearby-route.json?api_key=**MYACTUALAPIKEY**
D, [2019-05-30T12:12:22.882028 #96234] DEBUG -- request: User-Agent: "Faraday v0.15.4"
Content-Type: "application/x-www-form-urlencoded"
D, [2019-05-30T12:12:22.882207 #96234] DEBUG -- request: distance=5&fuel_type=ELEC&route=LINESTRING%28-80.19179+25.761683%2C+-80.191801+25.761682%2C+-80.191955+25.761671%2C+-80.192644+25.761626%2C+-80.193278+25.761585.....
The text was updated successfully, but these errors were encountered: