hi guys, darrell 's comment is spot on. but i just couldn't communicate it
owen
----- Original Message -----
From: "Darrell May" <[EMAIL PROTECTED]>
To: "'Michael Doerner'" <[EMAIL PROTECTED]>; "Gordon Rowell"
<[EMAIL PROTECTED]>; "Owen n Fleur Chambers +Patrick"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 01, 2001 12:01 PM
Subject: RE: [e-smith-devinfo] 4.1 b2
> Gordon, Michael, Owen,
>
> My guess is Owen may be trying to point out that the new console (at least
> the latest e-smith-base-4.1.2-4 I'm using) does not prompt for primary or
> secondary DNS entries during config.
>
> Darrell
>
> > -----Original Message-----
> > From: Michael Doerner [mailto:[EMAIL PROTECTED]]
> > Sent: Sunday, December 31, 2000 5:01 PM
> > To: Gordon Rowell; Owen n Fleur Chambers +Patrick
> > Cc: [EMAIL PROTECTED]
> > Subject: RE: [e-smith-devinfo] 4.1 b2
> >
> >
> > !> after installing 4.1 b2 on my network at home , the
> > server works great.
> > !>
> > !> I am running it in dedicated mode with a gateway, I am not
> > presented
> > !> with an option to enter the IP for a primary DNS server. I wish to
> > !> point it to by other e-emith 4.01 server
> >
> > !I don't quite understand that last sentence, but you should not need
> > !to configure DNS servers at all. e-smith is a caching DNS server and
> > !will set up its cache based on the Internet root nameservers.
> >
> > As I understand Owen's question (I might be wrong with my
> > assumption?):
> >
> > As many of us most probably do for testing a new e-smith
> > server version, we
> > set up a second box where we install the new software. This
> > installation
> > will start as a 'server only' installation because the other existing
> > e-smith server&gateway (= the production machine) is the one
> > that's still
> > responsible for all gateway functionality.
> > This production PC is also the one which acts as the local
> > DNS server for
> > all local Windows clients (and as a forwarder for all external DNS
> > requests).
> > When we add a second e-smith server, we would like to point
> > this machine's
> > DNS requests to the production server's DNS server. It's then
> > just another
> > node on our local network (but OS is Linux) like all the
> > other existing
> > nodes (their OS is usually Windows or Mac) who's DNS requests will be
> > resolved from the main server's DNS server.
> >
> > To achieve that, as far as I understand, we could disable
> > Bind on the new
> > installation and would have to change the template that creates
> > /etc/resolv.conf so that the contents of /etc/resolv.conf has
> > a content of
> > nameserver 'IP of e-smith production server'.
> >
> > With this, all own DNS requests of the new server will be
> > resolved by the
> > production server's Bind like all requests from the Windows
> > machines on the
> > LAN.
> >
> > Owen, is that what you were asking?
> >
> > Regards,
> > Michael Doerner
> >
> >
> > --
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
