![]() ![]() NB: nslookup does not look at the hosts file. You can check the current data in the DNS cache with: ipconfig /displaydns | more If yes, your hosts file is fine and the problem is elsewhere.Īlso, you can reset the NetBios cache with (open the console as an admin or it will fail): nbtstat -R To check if it works, use (assuming you have an ipv4 entry in your hosts for or an ipv6 entry in your hosts for ): ping -4 -n 1Īnd see if it uses the correct IP. Open a command line (Windows+R, cmd, Enter) and type: ipconfig /flushdns Did you check that it works correctly?Ĭhanges to hosts should take effect immediately, but Windows caches name resolution data so for some time the old records may be used. Based on my own experience and what I encountered while Googling, here are some things to try: 1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |