On Wed, 14 Mar 2001, Nathalie Boulos spewed into the bitstream:
NB>> How many hosts are on your LAN?
NB>
NB>there are 2 Red Hat 6.2 (one as a mail server (sendmail) the other Apache).
NB>Both are configured as DNS cache. There are also windows servers (DHCP and
NB>SQL).
NB>My segment is connected via router to another ethernet segment where there's
NB>the main DNS server for the whole network.
The delay is caused by Linux attempting to resolve the hostname for the
host that's connecting to it. To fix this (since there seem to be so few
machines involved) simply make an entry in your hosts files on the linux
boxen for each of the clients which need to connect. I do this all the
time and that's the quickest fix I know of.
I think that small networks, or small segments don't really merit DNS
unless they're doing it as a learning exercise for the admins. Host
files work fine for this. For example... in my own office... which
provides connectivity for my family also since my office is in my house,
I use hosts files for everything on the LAN. The only DNS here is a
cacheing DNS running on the firewall which forwards to my external
network (which is where all the real work gets done anyway). So the
hosts on my lan use host files unless the target is "off-lan" in which
case they use the cacheing DNS on the firewall.
--
Chuck Mead, csm -AT- moongroup.com, Owner, MoonGroup.com
(Note: html formatted email sent to me is filtered & deleted unread)
GnuPG Public Key Available: http://wwwkeys.us.pgp.net
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
