Decide if your machines will be connected to the internet DIRECTLY, or thru
a private LAN.
Direct connections will mean that you'll have to register your DOMAIN name
and IP addresses with the internic.
There will probably be an associated cost with your ISP to have multiple
connections.
As a result, most home users don't do this. Rather they resort to having
only one internet connected machine. Masq provides internet connection
sharing in Linux. Masq'd machines are not really "ON" the internet, though
they behave like they are.
If this machine will have two interface cards, one to the local lan, and one
to the internet, you do the following.
FIRST install the one interface card into your system.
Set up Linux and give your machine an arbitrary name and domain name.
Say: "mylinuxbox.joesplace.com"
By default then, "mylinuxbox" becomes the hostname and "joesplace.com"
becomes the domain name for your eth0 interface.
Since this interface is never "seen" on the internet, this does not cause
any problems.
Configure your other machines on the protected private lan to be members of
the "joesplace.com" domain.
You finish configuring your machine, and Linux is happy.
Then comes the time to set up your DSL/CABLE modem.
Pop in the other Ethernet card, connect the DSL/CABLE modem to it (via a hub
or xcross cable) and give it the hostname of "bcurry" and domain of
"mediaone.net".
Then enable dhcp on the eth1 interface.
Though bcurry.mediaone.net might be wrong, dhcp will adjust the host &
domain name correctly when the connection is first started.
Thus once you connect to the internet, you may find that your hostname will
change!
You may want/need to fix things so this does not happen, or use what the ISP
"gives" you.
If you are going to run an HTTP, FTP or other internet SERVER you'll need to
register your domain with the internic. You'll also need to get your ISP to
"FIX" your IP so it doesn't change. You then register your IP with the
internic (also get your ISP to add an entry into their DNS...).
Each of these will cost a few dollars.
If you are not going to run these services, then you can utilize any domain
name you want...
...esp. if you will be using dhcp to grab an IP from the ISP.
Linux MUST have a host & domain name of some sort to prevent those long
pauses. Even then you'll still see one or two during startup, as services
start up which look for a DNS...
-JMS
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bob Currey
Sent: Sunday, January 21, 2001 5:45 PM
To: [EMAIL PROTECTED]
Subject: RE: [newbie] Help! new 7.2 system has gotten abominably slow
As I'm reading this, the install's host name prompt screen sits in front of
me. Because of my setup, I am always lost in the how-tos as far as host
name is concerned. At the moment, I'm loading a new server. For the time
being, it will have eth0 connected to my home net, getting an IP address via
the DHCP server on my other Linux box which is currently the server. The
2nd NIC at eth1 is not connected at present, and won't be used till I
replace the old server with this new one, and then eth1 will run a DHCP
server for the home LAN.
The fact that I don't have a Domain has caused me tremendous grief, in that
setting up Apache, Samba, a DNS server, the FTP server, the Proxy server,
etc, all expect one, when you read the how-tos. For someone not a Linux
guru, it makes the stuff incomprehensible, as nothing fits. For that
reason, I ended up giving up at least for the time being on installing them
on my server (both the old one and new one), but would be very grateful if
someone could explain what I'm supposed to fill in when they want you to put
in your domain name in these setups. I spent many hours reading and never
understood how to set them up as a result. I imagine anyone else with a
home LAN that doesn't have a domain name (and this would be normal, I'd
expect) would be having the same trouble.
