I've got a machine here that's running a website. It's only really a development machine but it has IIS on it for testing purposes. Problem is that when pages get loaded in internet explorer using the machines name, the request is going out to the proxy server which is coming back with an error:

The requested URL could not be retrieved

While trying to retrieve the URL: http://seed-dev1.hull.ac.uk:5555/

The following error was encountered:

Unable to determine IP address from host name for seed-dev1.hull.ac.uk The dnsserver returned:

Name Error: The domain name does not exist. This means that:

The cache was not able to resolve the hostname presented in the URL. Check if the address is correct. Your cache administrator is webmaster.

Generated Thu, 04 Jun 2009 16:18:33 GMT by slb-webcache-east.hull.ac.uk (squid/2.6.STABLE22)

The error makes sense as the machine is really seed-dev1.net.dcs.hull.ac.uk. Regardless, I don't want it to be going off to the proxy server for local addresses. Not only is 'Bypass proxy server for local addresses' ticked on the proxy settings, but I've added exceptions in addition so it shouldn't be using the proxy for addresses beginning with: '*.hull.ac.uk; localhost;; seed-dev1' I can confirm that the exceptions are at least working because I can get to any pages within hull.ac.uk which I wouldn't be able to if I hadn't put it in the exception list.

As that doesn't work, I went further by going to the hosts file at C:\Windows\system32\drivers\ect

and added a line changing it to: localhost SEED-DEV1

A quick restart and it still doesn't work. Any pages that I try to access using the machine name just get that bad page returned from the proxy. Using localhost is all well and good for a single page but then you click on a link and it just switches back to the machine name in the url.

Any suggestions of stuff I could try would be much appriciated

5 Answers 5


Let's try the easy ones first:

(In Internet Explorer; and I'm assuming you're using IE because you're running IIS on and you reference the hosts file in \drivers\etc.)

1.) Navigate to "tools", "internet options", "connections", "LAN Settings".

2.) Make sure, "Bypass proxy server for all local addresses" is selected.

Now, hmm. Assuming you're running an internal DNS server/private IP addresses:

3.) In a command-prompt, run: "ipconfig /registerdns"

4.) Ensure that you can forward and reverse ping your machinename w/ it's internal IP address.

5.) If "localhost" isn't working, try pinging localhost at the command prompt, it's resolving to, yeah?

Let's clean up that hosts file:

5.) Make sure your hosts file wasn't inadvertently saved with a ".txt" extention. If so, remove it.

6.) In your LAN/adapter settings, make sure that you don't have any DNS suffixes to be appended.

Curious to see if any of those fixed the problem..


Check your IE Zones - I've seen it happen at times that IE would place a local server in the Internet zone, thus causing it to ignore the "bypass proxy" setting. Haven't figured out the reason why yet, but it does appear related to either a non-standard port or the server not being a member of the same Windows Domain as the client. To be honest, this is not something I've spent too much time researching; once I found a solution I moved on.

You should be able to explicitly add this server to your Intranet zone and thus trigger the proxy bypass; otherwise you will need to explicitly add the FQDN of the server to your "bypass proxy" list.


This isn't entirely related, but this question came up on top of my google seach.

From https://support.microsoft.com/en-us/kb/262981:

When you connect to a Web server using the Internet Protocol (IP) address or Fully Qualified Domain Name (FQDN) on the local network, Microsoft Internet Explorer or Windows Internet Explorer connects through an assigned proxy server even if the Bypass proxy server for local addresses option is turned on.

However, if you connect to a Web server using the host name (for example, http://webserver) instead of the IP address (for example, or FQDN (for example, http://webserver.domainname.com), the proxy server is bypassed and Internet Explorer connects directly to the server.


To bypass a range of IP addresses or a specific domain name, specify the addresses in the proxy exception list:

In Internet Explorer, on the Tools menu, click Internet Options. On the Connections tab, click LAN Settings. Click Advanced, and type the appropriate information in the Exceptions area.


In the early days of IE, a local server was defined to be "a server without periods in the name". in your example "http://seed-dev1/" would be local and "http://seed-dev1.hull.ac.uk:5555/" would be remote and sent to the proxy server.

In the IE Internet Options dialog, click on the Advanced button next to the port number text box for the proxy setting. You should see a text box at the bottom of this new dialog box that allows for exceptions. Try entering seed-dev1.hull.ac.uk in that box and clicking the OK buttons until you get back to the main IE window.

thanks, mark


This will happen if your proxy exception list is injected manually through the registry and is missing a ; semicolon after the last value. The reason is that the registry stores the checkbox at the end of the registry exception string as <local> and this is never properly parsed if the last semicolon is missing.

The registry key for an individual user can be viewed here:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

... or for environments that set this computer-wide:



This is most likely a bug with IE11, but one in which they're unlikely to fix. When adding exceptions manually, the UI will insert this semicolon silently.

Other symptoms that may occur are... websites like http://intranet may incorrect get a .com suffix appended or display 404 Page not Found (depending on the proxy software). Some pages and redirects will stop functioning and you may even find yourself un-clicking "Enable Protected Mode", but it's not that... it's the semicolon.

If this started happening in 2018, it may be triggered by a Windows update, although it's impossible to know without the source code or consulting Microsoft. Here's the Windows update text from July 2018 that reads as a possible culprit...

July 10, 2018—KB4338818 (Monthly Rollup) Addresses an issue where DNS requests disregard proxy configurations in Internet Explorer and Microsoft Edge.

You must log in to answer this question.

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