[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: hostname/netname



On Mon, Sep 11, 2000 at 07:51:08PM -0400, Gregg C wrote:
> Just your hostname goes in hostname (simple enough)

gotcha.

> Put your domain name in /etc/hosts put a line like:
> 
> 192.168.1.1	server.dontUthink.com	server

do i hafta be my own nameserver to do that? (i am, but i'm
asking if it's necessary.) or if i wanted to be a node off
my isp's zone: "mynode.isp.com" how much cooperation do i need
from the isp? and what files do i need to update to reflect
that?

> Who is doing your DNS? Do you have a permanent link to the internet? That 
> will determin how to do your resolv.conf file.

i think this may be the crux of what i'm after...

with my public zone (dontUthink.com) and a private zone (keep.out)
and my own forwarding name-server relying on my isp (morons-r-us.goof)
what should my resolv.conf be like?

> There are several reserved networks you can use. The most common is to use 
> one of the nets in 192.168.x.x.

i've got the IP number scheme down pretty well:
	192.168.1.1 eth0 == 208.33.90.85 eth1, same debian box

but i'm wondering about NAMING schemes:

the internet sees only dontUthink.com at 208.33.90.85; at the other
end of the linux pipe is 192.168.1.1 which services my intranet cpu's
at 192.168.1.100 and 192.168.1.200 as firewall and ipmasquerading router.

what standardization is there for naming, say, 192.168.1.100 in this case?
bubba1.dontUthink.com? offshoot.private.net? something.else.entirely?

what ramifications are there for naming private INTRAnet ip's as
	1) part of the public internet zone
	2) separate from the internet zone
?

and where do i set these names?



Reply to: