| Hosts File |
Article Index for Hosts |
Website Links For Hosts |
Information AboutHosts File |
| CATEGORIES ABOUT HOSTS FILE | |
| domain name system | |
| configuration files | |
|
HISTORY The ARPANET (predecessor to the Internet ) had no domain name system for giving Network Node s their own addresses. Because there was no centralized system for this purpose, each network node contained its own “map” of the network nodes that it needed to know about, and assigned them names that were memorable to the user. There was no system for ensuring that all systems on a network were called the same thing, nor was there a way to read some other user’s hosts file to automatically obtain their copy. The small size of the ARPANET permitted hosts files to be used with some convenience for some time. Network nodes typically had one address, and could have potentially many names. As individual TCP/IP computer networks started becoming popular, however, the hosts file became a large burden on system administrators—networks and network nodes were being added all the time—making maintenance of the hosts file a task which grew significantly. OTHER USES FOR THE HOSTS FILE The hosts file has alternative uses, including filtering ads by having entries for known ad-servers redirect to machines without the Advertising on them or more typically by redirecting references to ad-servers to the local address 127.0.0.1. This can save network bandwidth, as well, by eliminating a request to the DNS server normally used for obtaining address information, as well as by not downloading the advertisements. However, if the hosts file is to be used for this purpose, it must be kept up-to-date with lists of Internet servers known to host such content. A more important use of the hosts file is to block known-bad domains and servers in the same manner used for blocking ad-servers. The hosts file can also be “hijacked”, or used for malicious purposes. For example, Adware , Computer Virus es, Trojan Horse s, or other Malware can edit the hosts file (particularly on Windows -based systems) to redirect traffic from a “safe” site (such as Google or Wikipedia ) to sites hosting content that may be offensive or intrusive to the user or the user’s computer system. For example, a trojan (Qhosts) redirected traffic from search engines such as Google and AltaVista to a site specified by the author of the trojan horse. Mydoom.B (a malware program) blocked users from visiting sites regarding Computer Security and Antivirus Software , which also affected the Windows Update web site. Typical location host file in Windows system is C:\Windows\system32\drivers\etc\ folder or C:\Winnt\system32\drivers\etc\ The format of this file looks like: SEE ALSO
REFERENCES AND FOOTNOTES EXTERNAL LINKS
; Custom hosts files
; Applications to Manage Hosts Files
|
|
|