On Fri Oct 11 2002 at 12:10, "webmaster" wrote:

> Didnt find the /etc/hosts file. Is it in another
> location?

Then you have some major problems, this file is an important system
file and its absence has the potential to cause all sorts of grief.

As a atarting point, create it with this example entry:

127.0.0.1 localhost.localdomain localhost myhostname myhostname.rr.com

It is vital that localhost resolves to 127.0.0.1 and then to its
FQDN (fully qualified domain name).

You can then add other IPs and hostnames as you want, but don't add
too many.  If you don't have DNS running in a very small network,
then /etc/hosts is the only way to have hostname resolutions
working.

> ---------- Original Message ----------------------------------
> From: Keith Winston <[EMAIL PROTECTED]>
> X-Reply-To: [EMAIL PROTECTED]
> Date: 11 Oct 2002 05:46:25 -0400
> 
> >On Fri, 2002-10-11 at 02:18, webmaster wrote:
> >> This the error in the error log:
> >> (22002) Name or service not known: mod_unique_id: unable to
> >>     fine IPv4 address of "(my server name here)"
> >>
> >> I did change over my Linux box from NAT to public IP.  What
> >> name do I need for the server now?
> >
> >You should not have to change your server name, but you need to update
> >/etc/hosts to reflect the new IP address.
> >
> >Best Regards,
> >Keith
> >--
> >LPIC-2, MCSE, N+
> >Sing blue silver
> >Got spam? Get spastic http://spastic.sourceforge.net

(Spamassassin does a GREAT job for me for junking spam :)

Cheers
Tony




Reply via email to