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

Re: hostname/netname



On Tue, Sep 12, 2000 at 12:44:47AM -0500, Will Trillich wrote:
> thanks for your info! now i've got some fine-tune questions--
> 
> On Mon, Sep 11, 2000 at 11:21:40PM -0400, Gregg C wrote:
> > If you want people to be able to surf www.dontuthink.com, email 
> > will@dontuthink.com, telnet to server.dontuthink.com,  etc then you need 
> > DNS. Your ISP could do it, but its generally better/easier just to do it 
> > yourself.
> > 
> > your resolv.conf would be:
> > 
> > domain dontuthink.com
> > search whatever.lan
> > nameserver 192.168.1.1
> 
> how about
> 	domain dontUthink.com
> 	search lan
> 	nameserver 127.0.0.1
> 	nameserver ip.name.server.addr
> ?  is 127.0.0.1 bad compared to 192.168.1.1 for lan-wise dns?
> or does it not make any difference?

the only difference is if you have other computers networked
to your linux machine; they'll be able to connect to 192.168.x.x
but only your linux box can touch its own <insert erotic metaphor
here> 127.0.0.1 'interface'. you can also have linux treat different
interfaces differently: on mine, i've got spawn of satan (aka
telnet) listening for connections on port 23 of interface
192.168.1.1 but not on my public 208.33.90.85 connection.
you can also do different things with the 127.0.0.1 if you like.

> > This will allow you to work locally for telnet, bubb1, etc but will respond 
> > to the outside world with dontuthink.com
> > 
> > /etc/hosts:
> > 208.33.90.85 server.dontuthink.com
> > 192.168.1.1  server.whatever.lan	server
> 
> and
> 	127.0.0.1 loopback
> right?

sure.

and i'll put on my asbestos now, but i like to have mine look like
	127.0.0.1      localhost
	208.33.90.85   server   server.serensoft.com
	192.168.1.1    linus    linus.lan
	192.168.1.2    wdt      jonathon.lan
	192.168.1.3    kat      libris.lan
	192.168.1.4    jrmac    junior.lan
	192.168.0.1    diode    dave.munge.speedex.net
and /etc/networks like
	speedexish 208.33.90.0
	lan        192.168.1.0
	tunnel     192.168.0.0
with the shorter names left of the long names; otherwise most
net listings get a bit mangled with long address names.

	$ last
	will   pts/0      wdt              Thu Oct 12 11:33 - 17:29  (05:56)
	kat    ftpd5406   kat              Thu Oct 12 11:18 - 11:20  (00:01)
	kat    pts/2      diode            Tue Oct 10 15:54 - 15:57  (00:03)
	will   ftpd20580  diode            Mon Oct  9 13:33 - 13:34  (00:00)
	will   pts/0      wdt              Mon Oct  9 13:26 - 23:10  (09:44)
	rdt    ftpd22513  209-6-136-153.s1 Wed Oct  8 16:24 - 16:26  (00:02)    
	rdt    pts/1      209-6-136-153.s1 Wed Oct  8 16:13 - 16:39  (00:26)    

here, column 3 is kept managably terse, except for a ppp-like
connection for rdt.

same for other listings.
	$ route
	Kernel IP routing table
	Destination  Gateway         Genmask        Flags Metric Ref  Use Iface
	speedexish   *               255.255.255.0  U     0      0      0 eth1
	lan          *               255.255.255.0  U     0      0      0 eth0
	tunnel       *               255.255.255.0  U     0      0      0 dave
	default      router.serensof 0.0.0.0        UG    0      0      0 eth1

if i'd had a shorter name for router.serensoft.com it wouldn've been
chopped off...

> also, doesn't the sequencing mean something?
> 	208.33.90.85 server server.dontUthink.com
> makes display apps (ipfwadm -l for example)
> show 'server' instead of trying to use the
> full name 'server.dontUthink.com', yes?

there is a manpage on hosts (man hosts) that might give
away the store, there. i think you're right. also try
	apropos hosts
	apropos resolve
	apropos domain
and see if any other likely suspects pop up.

> mine also has the 'new style' gunk:
> 	::1 ip6-localhost ip6-loopback
> 	fe00:: ip6-localnet
> 	...

mine too. when i need to know what that's all about,
i'll check into it... good luck--  :)

-- 
things are more like they used to be than they are now.

will@serensoft.com *** http://www.dontUthink.com/



Reply to: