On Mon, Jan 01, 2001 at 10:29:20AM -0500, Gordon Rowell <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 01, 2001 at 02:00:51PM +1300, Michael Doerner <[EMAIL PROTECTED]>
>wrote:
> > [...]
> > 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.
>
> We also need to ensure consistency of WINS/DHCP details as well.
Whoops. Sorry for the short reply - brain/fingers interface
problem. Let's try again now that I understand your issue of
migration. We have had quite a few problems with people configuring
Primary/Secondary DNS to point to a box which only knows part of the
namespace.
We have also have had people configure forwarders to ISP machines
which are not complete DNS servers and in most cases, letting e-smith
work it out is correct.
We have various areas which need to be kept consistent, DNS, DHCP, and
WINS. For this to work properly, we need to be able to delegate those
nameservices to another box and we've already given some thought to
that. Just delegating DNS will cause inconsistency of naming for
Windows clients as WINS also creates names which must be managed.
> > Owen, is that what you were asking?
Gordon
--
Gordon Rowell [EMAIL PROTECTED]
http://www.e-smith.org (development) http://www.e-smith.com (corporate)
Phone: +1 (613) 564 8000 ext. 4378 Fax: +1 (613) 564 7739
e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada
