From owner-freebsd-isp Wed Jul 21 19:16:28 1999 Delivered-To: freebsd-isp@freebsd.org Received: from ns1.antisocial.net (ns1.antisocial.net [208.10.211.34]) by hub.freebsd.org (Postfix) with ESMTP id 8AB9B14C48 for ; Wed, 21 Jul 1999 19:16:24 -0700 (PDT) (envelope-from modred@ns1.antisocial.net) Received: from localhost (modred@localhost) by ns1.antisocial.net (8.9.3/8.9.3) with ESMTP id VAA16509; Wed, 21 Jul 1999 21:16:23 -0500 (EST) Date: Wed, 21 Jul 1999 21:16:23 -0500 (EST) From: Modred To: David Wolfskill Cc: freebsd-isp@FreeBSD.ORG, webmaster@deancare.com Subject: Re: Internal DNS In-Reply-To: <199907211516.IAA55453@pau-amma.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 21 Jul 1999, David Wolfskill wrote: > I'd expect that running a secondary for domB.com would be the thing to > do (assuming that they may well have DNS information for internal > consumption that isn't published out on the Internet). For what he's asking, I'd agree... On another note... Forwarding may help a bit too... he said 'connected to' another domain. Did you accquire a new domain/partner? Is the connection between domA and domB good? If so, sharing cache may increase performance. > Beware, though: if folks in domA.com were used to referring to machine > bar.domB.com as merely "bar" (from habits or code from domB.com, for > example), and want to do this even from within domA.com, you may get If 'bar' isn't in domA and domB, 'search domA.com domB.com' may help ease the transistion... Murphy's law suggests their favorite hosts will exist in both domains. ;) Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message