Windows 11 and 127.0.0.1 DNS

  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

PeterUK

Member
Oct 30, 2024
6
1
So I likely was having this problem before reinstalling but stopped to think about this odd problem I was seeing on a new install that I found and fixed that might be interesting for others.

So I run a BIND on windows 11 which is a shame they dropped support for windows but any how it worked and that my DNS server. Next I have my main PC windows 11 thats just been reinstalled and its setup has a lot of interfaces VLAN and DNS so

one interface is the main internet with DHCP DNS set to 127.0.0.1 no reply
another interface untag have DNS 192.168.255.49 that works with 192.168.255.60 as no reply until fail over by my routers.
Another interface VLAN53 with DNS 192.168.53.14 that works with 192.168.53.26 and 192.168.53.17 as no reply until fail over by my routers.

The problem
So everything works but every now and then after many sites the browser Edge or Chrome would pause loading a site for over about 5 seconds now some sites do take time to load but this was happening to simple or good fast sites. I tried many things and could not understand the problem I tried a reg setting NetFailureCacheTime to 0 but still it happened. Then looked at Wireshark loopback and see many requests to 127.0.0.1 which OK sure because I set that really it should use 192.168.255.49 and 192.168.53.14 when 127.0.0.1 fails which it does....

So I installed BIND simple setup for 127.0.0.1 to forward only to 192.168.255.49 and the problem went away!
 
  • Like
Reactions: chinatablet94