Re: hostname doesn't stick



From: "Gene Heskett" <gene.heskett@xxxxxxxxxxx>
On Sunday 17 September 2006 02:31, jdow wrote:
From: "Tim" <ignored_mailbox@xxxxxxxxxxxx>

Tim:
127.0.0.1 localhost.localdomain localhost

For some reason, Fedora likes to put the machine name into the
127.0.0.1 line, sometimes, despite all the problems that it can
cause.

jdow:
Did you do something silly like modify /etc/sysconfig/network? What
does it currently say? It should say:
NETWORKING=yes
HOSTNAME=localhost.localdomain

If not you did something to modify it and you have localhost being
renamed. Otherwise you may have nasty little spirits camping out
digitally on your machine.

Nup, nothing like that. I've seen quite a few machines that have the
machine name inserted there, by the routines that configure the network
settings for you on a freshly installed machine.

Usually, the first time around, your machine is localhost.localdomain,
but sometimes if you've entered a hostname, even if you have a NIC, the
hostname is inserted into the local loopback address details. Usually,
*before* the localhost.localdomain details (of all the worst places to
do so).

Given what the hosts file is for the ORDER does not matter. But the
127.0.0.1 line MUST be present.

The hosts file is merely used for looking up names on the local network
if you do not have the local network defined in an active DNS server.

(With 40 odd (and some even {O,o}) gadgets and computers on the network
here local DNS AND DHCP really makes it happen.)

Chuckle. And at the tv station, the hosts files are in kilobytes what with probably over 100 machines on several different subnets. DHCP is nice, but it doesn't lend itself to compiling a list on the wall so you KNOW where 192.168.17.33 is when it goes all aglay from some %$#@ winderz virii blasting the network. Its been worth its weight in bottled beer or sliced bread many times.

I have DHCP setup to assign known machines known addresses. I also
have it setup with a block for new or visitor machines to get usable
addresses within. I have not setup DNS so that it can be notified
from local addresses of newly registered machines. That is possible.

(I keep many copies of the zone files for the local network for just
the sort of reason you cite. Although I don't have the "marketdroid"
problems you face.)

{^_^}

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



Relevant Pages

  • Re: using the domain.local on the sbs server
    ... The reason that .local or .lan are recommended is that you have ... accessible via dns and not resolve to the local network. ...
    (microsoft.public.windows.server.sbs)
  • Re: hostname doesnt stick
    ... On Sunday 17 September 2006 02:31, jdow wrote: ... Fedora likes to put the machine name into the ... Given what the hosts file is for the ORDER does not matter. ... The hosts file is merely used for looking up names on the local network ...
    (Fedora)
  • Re: Can not see my own websites after setting up routing
    ... If I understand your post correctly, you have a DNS issue. ... Networking, Internet, Routing, VPN Troubleshooting on ... I have setup counting on Machine1. ... I have websites setup on Machine2 on my local network and am routing all ...
    (microsoft.public.win2000.ras_routing)
  • Re: routing problem
    ... >> I get an ipaddress and dns and gateways from dns but nothing beyond. ... >> I can ping any machine on the network but I cannot ping the other side of ... I can even pull down the web page of my local server ... >> outside the local network. ...
    (microsoft.public.windows.server.networking)
  • Re: NFS problems on FC1/5
    ... am on a local network, and tried to set up nfs between the two. ... I set the host to * in /etc/exports (like in mandriva), and had an almost identical rest of the file. ... the default Firewall settings of Fedora Core block NFS server/client responses. ...
    (Fedora)