From owner-freebsd-isp Fri Feb 13 13:10:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08324 for freebsd-isp-outgoing; Fri, 13 Feb 1998 13:10:35 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from proxyb2-atm.san.rr.com (proxyb2-atm.san.rr.com [204.210.0.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08301 for ; Fri, 13 Feb 1998 13:10:21 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (dt050ndd.san.rr.com [204.210.31.221]) by proxyb2.san.rr.com (8.8.7/8.8.8) with ESMTP id MAA00556; Fri, 13 Feb 1998 12:57:49 -0800 (PST) Message-ID: <34E4B3CA.110375AB@san.rr.com> Date: Fri, 13 Feb 1998 12:57:46 -0800 From: Studded Organization: Triborough Bridge and Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE-0213 i386) MIME-Version: 1.0 To: "Darrin R. Woods" CC: isp@FreeBSD.ORG Subject: Re: BIND question References: <3.0.32.19980213133416.0069a384@netgazer.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Darrin R. Woods wrote: > We seem to be having a problem with some of the websites that we host not > having a 'dns entry'. It's virtually impossible to debug DNS problems without knowing the hostnames you're having problems with, and the names/addresses of your dns'. > The problem only seems to be certain sites and only from certain ISPs. I > have tried setting my nslookup server Nslookup is not really a good diagnostic tool for dns problems. > We are running BIND 8.1 on FBSD systems. I hope you mean 8.1.1? > I am running out of ideas and > customers are getting pissed because people from some large ISPs can't get > to their website. Understandable. Try providing more details and we'll try to help. My first suggestion would be that there is probably an error in the zone file(s) for the domains you're having problems with. Try upping the serial number on one of those zones, and doing 'kill -1 ; tail -f /var/log/named.log'. This should show you where the error is. If you don't see the error doing it that way, try tail'ing the log in one window and -hup'ing in another. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message