Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using the .net SDK to talk to S3, but too often I get the following exception:

The remote name could not be resolved: ''

I'm using the two standard OpenDNS DNS servers, and falling-back to my ISP's DNS (verizon fios). Something is up here. When I ping the requests time out. Thoughts on what might be going wrong or other diagnostics I can run?

share|improve this question
Can you try other websites and Google's DNS? – digitxp Aug 25 '11 at 14:30
Other websites resolve just fine. I could try Google DNS and see if it helps...but I thought OpenDNS was supposed to be rock solid – SFun28 Aug 25 '11 at 14:36
@SFun28 Everything might fail, but you mention having a fallback DNS. Having them both fail is rather unlikely. Google's DNS could be another good fallback though, at least to debug (yes I'm aware the topic is a year old, but this might be useful for other readers). – Luc Aug 21 '12 at 17:15
Have you found any solution to this? It's 4 years later but I am getting the exact same error from time to time on my S3 bucket. – Thermometer Mar 25 '15 at 14:35

Unfortunately, Amazon disallow ping requests (at least to the S3 service).

Further reading can be found here:

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .