Loopback DNS Entries in Hosts File Not Supported

Confirmed Issue #8085332 • Assigned to Forbes H.


Lindsey T.
Jul 5, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 16 people

Sign in to watch or report this issue.

Steps to reproduce

  1. Open C:\Windows\System32\drivers\etc\hosts in text editor in administrative mode.
  2. Add an entry for host name that is not “localhost” with loopback IP of, i.e.: mycomputer, then save the file.
  3. Open a command prompt in administrative mode and execute ipconfig /flushdns to clear the DNS resolver cache.
  4. In IIS or another web server on the same machine, configure site bindings for a site to respond to the host name that was chosen. For instance, in IIS:
  • Right click the site you wish to use, such as “Default Web Site,” and choose Edit Bindings.
  • Click the Add button in the Site Bindings dialog.
  • Type the host name, i.e. mycomputer, in the Host name field of the Add Site Binding dialog, then click OK.
  1. Open Edge and type the protocol and host name into the address bar, i.e. http://mycomputer, and press enter. The browser should fail to resolve the DNS entry correctly.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

    • I seem to actually be getting completely different results. The domain will not load for me in Edge - but does in Chrome.

      Curious - do you have localhost loopback enabled in the about:flags section of the browser by chance?

    • Brad E.:

      Localhost loopback is enabled. And resolving the localhost name works fine. But any other non-localhost entries that loopback fail to resolve (as you describe). Our methodology is to utilize a subdomain with *.local.mycompanydev.com to set up local instances on our machines for testing and development of our applications, but this is unworkable in Edge as they will not resolve (possibly due to logic surrounding that configuration flag).

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Erik A.”

      Changed Assigned To to “Bruce M.”

    • I’m having the same problem, but I’m not even using a loopback address. I have a VirtualBox isntance running on my Windows 10 host, and host my development sites on that. I have entries in the hosts file for fully-qualified domain names (using our companies .com domain) pointing to a 10.0.x.x IP, which the Virtual Box host-only adapter. Works in every other browser but apparently not edge.

      And yes, I have Allow local loopback checked.

      Since neither a hosed virtual machine nor, from the OP, a local binding seem to work I can only conclude that Edge is broken for any serious web development. Something of an epic fail for a web browser…

    • I cannot repro on a newer preview build (14943). However, seeing another report via Twitter

    • I’m actually no longer experiencing this issue after upgrading to the anniversary edition build.

      Microsoft Edge 38.14393.0.0
      Microsoft EdgeHTML 14.14393

    • I am on Microsoft Edge 38.14393.0.0 and still have the issue

    • I actually just switched OFF the flag “Allow local host loopback” and it started working defying all logic.

    • I have this issue with Microsoft Edge 38.14393.0.0
      Same scenario as OP (local websites hosted in IIS 7.0 with Bindings set and hosts file entries that map to accordingly)

      Toggling ON/OFF the “Allow localhost loopback” in about:flags and then doing a full reboot has no effect.

      Chrome/IE11 - no issues

      Currently blocked from using Edge as a viable web browser for development.

    • Same here:
      Blocked from using Edge as a viable web browser for development.

    • Same here:

      Toggling ON/OFF the “Allow localhost loopback” in about:flags only has effect on “localhost” domain name, but not others domains defined in hosts file

      Blocked from using Edge as a viable web browser for development.

      more than one year opened issue and no more any news from MICROSOFT EDGE TEAM ?

    • Microsoft Edge Team

      Changed Assigned To from “Bruce M.” to “Forbes H.”

      Changed Status to “Confirmed”

    • Hi, is there some ETA for this issue? I can’t believe how is it possible that this basic feature is not supported…

    • Hi, any update for this issue? I am facing the same problem on Edge version Microsoft Edge 41.16299.15.0 under Windows 10 1709. This problem doesn’t exist on older version of Edge 38.14393.1066.0 under Windows 10 1607.

    • Microsoft Edge can’t access virtual host in vagrant virtualbox. I can access localhost:8000 but other host name like test.dev doesn’t work. Edge shows this error:
      Every other browser works.

    • The hosts file has this pgtest.test
      This is the ip of the homestead vagrant virtualbox
      Microsoft Edge can’t access this virtual host.

    • guys, check this answer on stackoverflow , it worked for me


    • I’m a web developer who uses Vagrant. [1]

      Every time I start vagrant the following lines of text are added to the c:\WINDOWS\system32\drivers\etc\hosts file:

      ## vagrant-hostmanager-start id: 944c7ecf-45de-4b3b-a57d-d2a1d41b898f    pressbooks.test    www.pressbooks.test
      ## vagrant-hostmanager-end

      The IP is not guaranteed to be static.

      When I type http://pressbooks.test in Chrome, Firefox, and IE it works.

      When I type http://pressbooks.test in Edge it does not work. I get INET_E_RESOURCE_NOT_FOUND

      I tried [2]

      CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"` 

      and it did not improve the situation. Help?

      [1] https://www.vagrantup.com/
      [2] https://developer.microsoft.com/en-us/microsoft-edge/platform/faq/#how-can-i-debug-localhost

    • I am also a web developer using vagrant and I am having the same problem as Dac C. Even after trying everything I could find around the internet. I am still getting the INET_E_RESOURCE_NOT_FOUND error.

      In our, mine and Dac C, case it is not using localhost but a VM hosted on a local virtual network that the host is aware of (using 192.168.50.x). It shows up in my hosts file and works for all other browsers.

    • Same problem INET_E_RESOURCE_NOT_FOUND with https://*.test pointing to a vagrant box in host-file. https://stackoverflow.com/questions/32384571/why-does-microsoft-edge-open-some-local-websites-but-not-others-where-the-doma/37848210#37848210 did not help!

    • Same issue on my end with °42.17134.1.0 MS Edge Windows 10, Microsoft EdgeHTML 17.17134

      The browser displays INET_RESSOURCE_NOT_FOUND
      whence trying to access a local page served by :

      1. Apache httpd 2.2
      2. IIS

      I am not sure if some kind of ipv6 restriction could be infer since edge is able to connect when asked to fetch localhost with the localhost not fully qualified name.

    • Still no luck using Homestead/Vagrant configuration.
      Standard loopback address ( with Apache serving can be fixed with 'CheckNetIsolation Loopback…’, but Vagrant’s no way - getting INET_E_RESOURCE_NOT_FOUND

    You need to sign in to your Microsoft account to add a comment.

    Sign in