I added a hostname entry for a linux vm in windows hosts file
For example
192.168.103.23 vbox.local
From Windows, pinging vbox.local required 3-5 secs to response.
However, a instance response by pinging 192.168.103.23
slow dns response from Windows ?
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: slow dns response from Windows ?
The hosts file is the last in a chain to find and resolve names. Don't expect it to be instantaneous.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: slow dns response from Windows ?
Um... actually the hosts file is the first one that is consulted. There are known lists of "hosts" files (which include adware/malware sites) which point to 0.0.0.0. That saves even the trip to the DNS server. But, definitely, pinging directly instead of using a name resolution is indeed faster. Further reading: http://en.wikipedia.org/wiki/Hosts_%28f ... plications
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.