3

Closed

The remote name could not be resolved: 'az320820.vo.msecnd.net'

description

When I try to install any package clicking button "Install", a getting the error: "Operation Failed"
"The remote name could not be resolved: 'az320820.vo.msecnd.net'" on red

UPDATED TROUBLESHOOTING TIPS FROM THE NUGET TEAM

If you experience this error, please run the following 3 commands from a command window, capture the output, and send the results. If email is preferred rather than posting here, you can email the results to support at nuget dot org.
  1. nslookup az320820.vo.msecnd.net
  2. nslookup az320820.vo.msecnd.net dns11.msecnd.net
  3. ipconfig /all
For the ipconfig /all output, the "DNS Servers" data is the relevant portion.

We are working with Windows Azure to diagnose the root cause of this intermittent issue and we appreciate your help.

file attachments

Closed Aug 30, 2012 at 10:26 PM by JeffHandley
Fixed. We ended up waiting a week to let the DNS name propagate. CDN is re-enabled now though.

comments

pranavkm wrote Aug 15, 2012 at 6:08 PM

Are you able to access the host from a browser? https://az320820.vo.msecnd.net/packages/jQuery.UI.Combined.1.8.22.nupkg

fabiosilvalima wrote Aug 15, 2012 at 6:45 PM

Hi pranavhm, I CAN'T NOT.
IE Error or some other browser:
"Internet Explorer cannot display the webpage"

I've tried to access that URL in other machines like cloud computing... but does not working...
:(

fabiosilvalima wrote Aug 15, 2012 at 6:51 PM

Really it seems to be DNS problem, I've tried of a machine in India (cloud) and worked.. it is a shame, I don't know how to fix it...

pranavkm wrote Aug 15, 2012 at 7:22 PM

We're working with the Azure team to figure out if this is something they can fix from their end. Do you think you could give us the region \ locale you are working on and possibly the DNS server that it's going up against?

diegose wrote Aug 15, 2012 at 7:44 PM

@pranavkm, @JeffHandley: tracert reports "Unable to resolve target system name az320820.vo.msecnd.net" from here (Buenos Aires, Argentina, my ISP is Fibertel)

I had to change my package source to preview.nuget.org so I could build my project.

joaofx wrote Aug 15, 2012 at 8:08 PM

I'm getting the same problem. I'm from Brazil.

JeffHandley wrote Aug 15, 2012 at 9:12 PM

We have disabled the CDN for nuget.org, so this problem should go away for you.

I suspect that the DNS entry that was created yesterday for the new CDN endpoint has not propagated and you are behind a DNS server that is aggressively reporting that the host doesn't exist rather than querying the authoritative server.

We will re-enable CDN in a week or so, giving the DNS entry some time to propagate.

fabiosilvalima wrote Aug 16, 2012 at 7:40 PM

@pranavkm I'm from Brazil, city of Sao Paulo.
@JeffHandley Now it's working! I installed some packages, no errors.

Thank you everyone.

JeffHandley wrote Aug 16, 2012 at 8:26 PM

Thanks for reporting this issue and helping us diagnose it!!

We will reach out to you when we re-enable CDN to make sure things are still working for you then.

diegose wrote Aug 16, 2012 at 8:41 PM

Thank you for fixing it.

FWIW, az320820.vo.msecnd.net is now visible.

JeffHandley wrote Aug 16, 2012 at 9:17 PM

Good to know, thanks @diegose!!

howarddierking wrote Aug 16, 2012 at 10:14 PM

** Closed by howarddierking 08/16/2012 2:14PM

kevinjong wrote Aug 17, 2012 at 3:35 AM

I still encounter this problem
I'm from Taipei, Taiwan.

JeffHandley wrote Aug 17, 2012 at 4:12 AM

Sorry about that @kevinjong. The CDN was temporarily re-enabled. I have disabled it again. Thing should be working for you now.

kevinjong wrote Aug 17, 2012 at 5:02 AM

It's work now.
Many thanks!

JeffHandley wrote Aug 23, 2012 at 6:40 AM

We will be re-enabling CDN tonight as part of the deployment (http://blog.nuget.org/20120822/nuget-expected-downtime.html).

Please let us know if you still experience issues connecting to the cdn host.

Oceanswave wrote Jun 19, 2013 at 2:20 PM

Just received this today from an automated build on the TFS Build Service:

C:\a\src.nuget\nuget.targets (80): The remote name could not be resolved: 'az320820.vo.msecnd.net'
C:\a\src.nuget\nuget.targets (80): The command ""C:\a\src.nuget\nuget.exe" install "C:\a\src\Server------------------\packages.config" -source "" -RequireConsent -o "C:\a\src\packages"" exited with code 1.

Oceanswave wrote Jun 19, 2013 at 2:22 PM

The automated build at 3AM succeeded, so something has changed since then...

JeffHandley wrote Jun 19, 2013 at 6:23 PM

Whenever this issue occurs, it's a DNS failure meaning your computer is unable to resolve the host name to an IP address. DNS resolution can occur at many different hops between you and the authoritative DNS server for the host.

When this issue occurs, you can open a command window and run the command "nslookup az320820.vo.msecnd.net" to see what the results are. This command will run the DNS lookup for the host and return the IP address. If this fails, please capture the response and post it here. This information can help us determine if the DNS issue is closer to your ISP or closer to the authoritative DNS server for the domain.

Thanks!

djbyter wrote Jun 24, 2013 at 9:44 PM

I'm also seeing this issue now using tfs.visualstudio.com, so I can't run that from the command-line. I have build the solution twice today, and only now is there an issue.

JeffHandley wrote Jun 25, 2013 at 11:55 PM

UPDATED TROUBLESHOOTING TIPS FROM THE NUGET TEAM

If you experience this error, please run the following 2 commands from a command window, capture the output, and send the results. If email is preferred rather than posting here, you can email the results to support at nuget dot org.
  1. nslookup az320820.vo.msecnd.net
  2. ipconfig /all
For the ipconfig /all output, the "DNS Servers" data is the relevant portion.

We are working with Windows Azure to diagnose the root cause of this intermittent issue and we appreciate your help.

gouderadrian wrote Jan 17 at 5:31 PM

In Visual Studio 2012, when I changed the address from https to http, I no longer get the error.

iicdkp wrote Aug 12 at 9:31 AM

Hello, it might seem odd that someone has the same issue 2 years later, but I'm experiencing exactly the same problem, using VS 2012 and 2013 as well...
I'm located in Cameroon. Could you please see if there is some restriction regarding my area?
Thanks.

allanmclemore wrote Sep 16 at 12:35 AM

I'm seeing the issue right now on Monday Sept 15, 2014. (e.g. 2 years later as well)
I'm in Texas.

allanmclemore wrote Sep 16 at 12:35 AM

Running Visual Studio 2013 on Windows 8.1.

allanmclemore wrote Sep 16 at 12:39 AM

Never mind. It's a firewall/proxy issue for me at least.

2 Things to consider:
  1. If you are working remotely and have any sort of VPN connection to your corporate network, kill it and try the nuget pull.
  2. If you are at work behind a company firewall, try doing the nuget pull from another network (at home, etc.)