On Wed, Nov 14, 2001 at 10:52:09PM -0800, Patrick Nelson wrote:
> I'm just not sure what is the best way to name systems on the private side
> of our LAN. We tried using just single names but some programs seem to have
> problems with it. Like NIS and SendMail. What is the best way to name
> systems on a LAN behind a firewall that don't have internet names?
Give them internet names! The extension can be anything you want. For
example, foo.nelson is a valid FQDN as long your local nameserver is
authoritative for the .nelson domain.
Personally, I registered a name through the NIC and that gave me the option
of bringing it online later without changing all the host names. So, for
exmaple, register patricknelson.org (assuming it's available), configure
all your internal hosts accordingly, and you're in business if sometime
down the road you want your internal hosts to have external connectivity.
Again, make sure your hosts have valid DNS. I personally use bind 9 in a
split mode - lookups from the internal network get returned internal
addresses (ie, 192.168.) and lookups from the external network get rejected
(although you could have them return external addresses).
Cheers,
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
