Powershell Invoke-WebRequest returns "remote name could not be resolved" but not proxy error

Question

I am trying to download a page using wget (alias for Invoke-WebRequest) in powershell. The page in question is www.privatahyresvärdar.nu.

When using Internet Explorer I can navigate to www.privatahyresvärdar.nu but I cannot run wget from powershell nor can i ping the site. Neither command can resolve the hostname.

I have followed several advice on SO and other sites commenting on using Proxies as an error source for wget failing, but i am not using any Proxy.

Please help me identify the error source!

LudvigH · Accepted Answer · 2017-01-10 18:46:59Z

5

After a moment of clarity it struck me that it might be an encoding error! After replacing the hostname with punycode with an online punycode encoder (first hit on google) it worked like a charm!

answered Jan 10, 2017 at 18:46

LudvigH

4,9345 gold badges39 silver badges60 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Post Impatica Over a year ago

I get this error whenever I have my azure vpn connected.

LudvigH Over a year ago

That sounds more like a proxy problem to me. Check out those quations and answers.

Collectives™ on Stack Overflow

Powershell Invoke-WebRequest returns "remote name could not be resolved" but not proxy error

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related