From owner-freebsd-isp Sat Feb 12 10:29:19 2000 Delivered-To: freebsd-isp@freebsd.org Received: from boris.netgate.net (boris2.netgate.net [204.145.147.155]) by builder.freebsd.org (Postfix) with ESMTP id 292803F21 for ; Sat, 12 Feb 2000 10:29:15 -0800 (PST) Received: from localhost (wellsian@localhost) by boris.netgate.net (8.9.3/8.9.3) with ESMTP id KAA42754; Sat, 12 Feb 2000 10:26:34 -0800 (PST) (envelope-from wellsian@caffeine.com) Date: Sat, 12 Feb 2000 10:26:34 -0800 (PST) From: wellsian X-Sender: wellsian@boris.netgate.net To: James Wyatt Cc: Gene Harris , "David A. Gobeille" , freebsd-isp@FreeBSD.ORG Subject: Re: DSL firewall and DNS In-Reply-To: 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 This is exactly what I've wanted to do for a couple installations, but I haven't felt secure about misrepresenting the primary/secondary relationship. Are there any technical reasons not to do what James suggests? Thanks, Dave On Sat, 12 Feb 2000, James Wyatt wrote: > On Sat, 12 Feb 2000, Gene Harris answered David A. Gobeille's DSL/DNS > questions with: > [ ... ] > > Now that I have a better idea about your service, you'll be > > a lot better off letting the isp be your 2nd DNS server. > > That way, if your machine blows up, folks can still view > > your web site, send you email, etc. > > Or have your ISP secondary from your primary DNS server on your DSL and > put their servers on the InterNic records... You will also have fewer > folks trying to hack your primary DNS server when it isn't listed. 8{) > > It lets you update easily while providing more reliable and faster DNS > host. (Not to knock your host, but the link adds a hop or two, a dozen or > so mS, and more pieces) Always reduce the path to DNS servers... - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message