|
Home > Archive > alt.os.linux > November 2002 > hostname question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Jason A. Arends 2002-11-28, 3:24 am |
| i have a cablemodem internet connection that i share with ipmasq. my
provider doesn't require me to use any specific hostname to make dhcp
work. inside my network, i have 1 linux and 2 windows boxes that get
their ips from dhcp on the firewall. my domain name changes with my ip
address: it looks something like this:
dhcp-aaa-bbb-ccc-ddd.blah.isp.net. should my hostname be set to this
FQDN? right now it's set to a domain i have at dyndns.org.
unfortunately, when my internet connection is down (which is rare, but
it happens) both my firewall and my linux computer operate very very
slowly when i'm running kde, i'm assuming it's because of hostname
timeouts or something.
what do i need to do to make this work like it should? should i change
my hostname when my ip changes, so it's the same? how can i make my
linux computers not be broken when there is no internet connection?
what should my hostname be for the computers inside the network, right
now, they're not using a FQDN, just one name. any suggestions from
people with similar setups?
| |
| Brian Patil 2002-11-28, 4:24 am |
| In article <as4jus$j9q$1@news.cfu.net>, "Jason A. Arends"
<arends@sheerer.net> wrote:
> i have a cablemodem internet connection that i share with ipmasq. my
> provider doesn't require me to use any specific hostname to make dhcp
> work. inside my network, i have 1 linux and 2 windows boxes that get
> their ips from dhcp on the firewall. my domain name changes with my ip
> address: it looks something like this:
> dhcp-aaa-bbb-ccc-ddd.blah.isp.net. should my hostname be set to this
> FQDN? right now it's set to a domain i have at dyndns.org.
> unfortunately, when my internet connection is down (which is rare, but
> it happens) both my firewall and my linux computer operate very very
> slowly when i'm running kde, i'm assuming it's because of hostname
> timeouts or something.
No such thing as a "hostname timeout".
Dhcp clients (eg dhcpcd) can be given a hostname to use for
DHCP purposes (dhcpcd -h xxxx). So your hostname does not change.
The exact details are Linux-distribution dependent.
>
> what do i need to do to make this work like it should? should i change
> my hostname when my ip changes, so it's the same? how can i make my
> linux computers not be broken when there is no internet connection? what
> should my hostname be for the computers inside the network, right now,
> they're not using a FQDN, just one name. any suggestions from people
> with similar setups?
>
All your hosts inside the network should have different names
but share the same domain.
| |
| Joe Fredrickson 2002-11-28, 5:24 am |
| Thu, 28 Nov 2002 07:26 pm will from hence forward be known as the day Jason
A. Arends blabbered:
> what do i need to do to make this work like it should? should i change
> my hostname when my ip changes, so it's the same? how can i make my
> linux computers not be broken when there is no internet connection?
> what should my hostname be for the computers inside the network, right
> now, they're not using a FQDN, just one name. any suggestions from
> people with similar setups?
Personally I dont even bother setting the hostname to anything remotely
similar to the actualy FQDN of my server (on DSL with similar IP) but
that is because I only use hostname for internal network remote calls.
Im not sure if you can change your hostname with DCHP to make it like
your machines FQDN but that doesnt mean you cant. Google would know the
answer.
--
remember this is the sequence of events, in no particular order
Registered Linux User 282072
<www.volutin.net -- everything irrelevant>
| |
| Martin Blume 2002-11-28, 2:24 pm |
|
Jason A. Arends <arends@sheerer.net> schrieb in im Newsbeitrag:
as4jus$j9q$1@news.cfu.net...
> i have a cablemodem internet connection that i share with ipmasq. my
> provider doesn't require me to use any specific hostname to make dhcp
> work. inside my network, i have 1 linux and 2 windows boxes that get
> their ips from dhcp on the firewall. my domain name changes with my ip
> address: it looks something like this:
> dhcp-aaa-bbb-ccc-ddd.blah.isp.net. should my hostname be set to this
> FQDN? right now it's set to a domain i have at dyndns.org.
> unfortunately, when my internet connection is down (which is rare, but
> it happens) both my firewall and my linux computer operate very very
> slowly when i'm running kde, i'm assuming it's because of hostname
> timeouts or something.
No, it's DNS (Domain Name Resolution), the process by which ip addresses
like 213.95.15.200 which can only be remembered by a computer get translated
into a name like www.suse.de and vice versa. Whenever you specify a name
like www.xyz.com your computer asks a name server first for translation and
then takes up connection with the ip address it gets in return. If the
internet connection is down, it has to wait for a timeout before it shows
you an error.
>
> what do i need to do to make this work like it should? should i change
> my hostname when my ip changes, so it's the same? how can i make my
> linux computers not be broken when there is no internet connection?
> what should my hostname be for the computers inside the network, right
> now, they're not using a FQDN, just one name. any suggestions from
> people with similar setups?
>
If your internet connection is down, you should reconfgure your DNS
processes to point to another name server (a local one) or base yourself on
files (/etc/hosts).
But basically it is easier to wait for the reestablishment of your internet
connection, as you can do only local work without internet connection.
As for the name, you can name the machines any way you like in your own
local net. I would set up the /etc/hosts file of your work station to
contain all computers on your local net, like
127.0.0.1 localhost
192.168.0.1 workstation
192.168.0.2 server
192.168.0.99 firewall
and have the line
order hosts bind
in the file /etc/host.conf. This tells your local name resolution (on the
workstation) to look first in the file /etc/hosts, where it will find all
your local workstations, and only in case it can't find them there
(misspelled, or host on the internet) it asks for an external nameserver.
Regards
Martin
|
|
|
|
|