74 lines
1.8 KiB
HTML
74 lines
1.8 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>hosts(5)</TITLE>
|
|
</HEAD>
|
|
<BODY>
|
|
<H1>hosts(5)</H1>
|
|
<HR>
|
|
<PRE>
|
|
|
|
</PRE>
|
|
<H2>NAME</H2><PRE>
|
|
hosts - hostname to IP address database
|
|
|
|
|
|
</PRE>
|
|
<H2>SYNOPSIS</H2><PRE>
|
|
<STRONG>/etc/hosts</STRONG>
|
|
|
|
|
|
</PRE>
|
|
<H2>DESCRIPTION</H2><PRE>
|
|
The hosts database lists the IP addresses and the hostnames that
|
|
translate to these IP addresses. It is used by <STRONG><A HREF="../man8/nonamed.8.html">nonamed(8)</A></STRONG> in a network
|
|
without name servers. A simple <STRONG>/etc/hosts</STRONG> may look like this:
|
|
|
|
127.0.0.1 localhost
|
|
192.9.200.1 darask
|
|
192.9.200.2 burask
|
|
|
|
The localhost entry lists a special address that refers to the local host
|
|
itself (a kind of /dev/tty for hosts.) You should only list it if
|
|
<STRONG>nonamed</STRONG> needs it! The other entries are actual machines. The file may
|
|
contain comments marked with '#'.
|
|
|
|
You can have aliases (more hostnames on the same line), but it is not
|
|
recommended, because <STRONG>nonamed</STRONG> can't present them to the system as CNAME
|
|
records. An often seen form like
|
|
|
|
192.9.200.1 darask.home.cs.vu.nl darask
|
|
|
|
is harmless though, and has the small advantage that you can use the
|
|
short name in <STRONG>/etc/ethers</STRONG> so <STRONG>rarpd</STRONG> can match it at boot time.
|
|
|
|
|
|
</PRE>
|
|
<H2>FILES</H2><PRE>
|
|
|
|
/etc/hosts Hosts database.
|
|
|
|
|
|
</PRE>
|
|
<H2>SEE ALSO</H2><PRE>
|
|
<STRONG><A HREF="../man5/ethers.5.html">ethers(5)</A></STRONG>, <STRONG><A HREF="../man8/nonamed.8.html">nonamed(8)</A></STRONG>, <STRONG><A HREF="../man8/rarpd.8.html">rarpd(8)</A></STRONG>, <STRONG><A HREF="../man8/boot.8.html">boot(8)</A></STRONG>.
|
|
|
|
|
|
</PRE>
|
|
<H2>AUTHOR</H2><PRE>
|
|
Kees J. Bot (kjb@cs.vu.nl)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
</BODY>
|
|
</HTML>
|