From owner-freebsd-isp Thu Dec 18 16:54:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA07611 for isp-outgoing; Thu, 18 Dec 1997 16:54:22 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA07605 for ; Thu, 18 Dec 1997 16:54:14 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id LAA07628; Fri, 19 Dec 1997 11:52:49 +1100 (EST) Date: Fri, 19 Dec 1997 11:52:49 +1100 (EST) From: "Daniel O'Callaghan" To: Wm Brian McCane cc: freebsd-isp@FreeBSD.ORG Subject: Re: Reverse name problem In-Reply-To: <199712182152.PAA02846@modem3739496.cavtech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 18 Dec 1997, Wm Brian McCane wrote: > I am having a problem with my DNS. I have setup both the primary and > secondary DNS to be machines on my internal network. One of my partners You need to tidy up a few things. In your zone file for uit.net, you list only dns.uit.net. InterNIC has dns.uit.net and mail.uit.net listed. You should make this consistent. Also, you should ask someone on the freebsd-isp list if they would be kind enough to secondary you. You really should have a remote secondary. The philosophy is: "Even if you are not reachable, you should be resolvable." Otherwise, if you have a problem, people won't even be able to find out your IP addresses, or MX records (ask your upstream provider to act as a mail relay and list a backup MX record). You really don't want people to see "Host not found" messages when you are down - much better to have a "host not responding". When you get a new secondary (or two) list them in your zone file and register the new data for uit.net with InterNIC. The same goes for 205.83.209 and any other domains you are hosting. Danny