>1. Get Bind and install it.
it ships with redhat
>2. Edit the bind so that I have a local private domain as well as my public
>one (split DNS?)
if you want. i don't. i just define my internal domain as
, thus my machines are ,
and thus still resolves to the address defined by my
isp,
On Fri, 16 Nov 2001 [EMAIL PROTECTED] wrote:
> David Talkington wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > >> 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
David Talkington wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> >> 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
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 fire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> 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 L
On Wed, 14 Nov 2001, 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 behin
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
> sy
Set up a zone, for which your main server is primary. You can do the same
for the reverse zone for the private network. Then, as long as you set
the main server as the primary name server in the client machines'
resolv.conf files, you should be ok.
On Wed, 14 Nov 2001, Patrick Nelson wrote:
On Thu, Nov 15, 2001 at 02:39:58AM -0500, Anthony E. Greene <[EMAIL PROTECTED]> wrote:
| On Wed, 14 Nov 2001, 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 probl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 14 Nov 2001, 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 th
Hi Patrick,
> 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 in
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?
12 matches
Mail list logo
