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?
127.0.0.1 is mainly for the loopback. using 127.0.0.1 will work. I just tend
to use the 192.168.x.x because that is what I use in the resolv.conf in
other boxes. But I can't think of a reason not to use 127.
> 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?
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?
mine also has the 'new style' gunk:
::1 ip6-localhost ip6-loopback
fe00:: ip6-localnet
...
Which I have little understanding of, currently. The order I use it above is
because foreign hosts will almost certainly be using FQDN, otherwise how to
they get to you as apposed to server.microsoft.com, etc.
But it still allows your other local systems to use just the machine name
and not get confused. When I first set up my lan, I had problems whenever my
ppp link was down, because my local systems knew the gateway as
machinename.domain.net, (didn't use .lan then) and that resolved to the
non-working interface.
In the /etc/hosts file, the order on the same line, doesn't really matter.
When you are looking for say an
You would generally want the ip look up to get the FQDN, so having it first
is a good idea.
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] <
/dev/null
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
