Back at Square 1

[zscoundrel]

No, this is an acceptable fix - IF - he is running that machine to be 
accessible only on his internal network.  According to the config file, 
You should use a fully qualified DNS name or the IP address if a 
registered DNS name is not available.

I have a really old box that I just want to use as a file server, and 
test platform.  It does NOT have a DNS name because it is located on my 
side of the firewall and I don't intend to ever register it with the 
network.  (Why waste the money on registration?)

One of the beautiful things about the 192.168.x.x network address is I 
don't HAVE to register with ANYONE to run a network!  Using DHCP on the 
Linksys firewall gives me access to the Internet for the machines that 
surf, and I still have local addresses for those machines that don't.

Perhaps not having a DNS name for a box would bother some people, but I 
find that getting to 192.168.1.69 and 
http://ars.userfriendly.org/cartoons/?id=20020319&mode=classic are 
equally easy to use - especially when they are accessed via a bookmark 
entry in my browsers bookmark file!  (Or a script)

Some people go the whole nine yards and set up their own DNS server and 
domain name.  I just use what I get from RR for the firewall and DHCP 
does the rest.

Jonathan  wrote:

> Sounds like you've still got some issues - shouldn't have an IP as the
> hostname to begin with.
> 
> I strongly suggest doing 'rpm -e linuxconf' first.  If you use anything but
> linuxconf to attempt to configure your networking, then run linuxconf, you
> will end up with mixed and conflicting settings in various places.
> 
> Most linux distributions have seen the light and ditched linuxconf with
> prejudice - it was a Bad Idea.
> 
> 
> 
> 
>