From owner-freebsd-questions Sun Apr 26 14:00:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14727 for freebsd-questions-outgoing; Sun, 26 Apr 1998 13:36:24 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14528 for ; Sun, 26 Apr 1998 13:34:32 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA15783; Sun, 26 Apr 1998 13:34:30 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <35439A56.35ECB815@san.rr.com> Date: Sun, 26 Apr 1998 13:34:30 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0420 i386) MIME-Version: 1.0 To: "Saffa J. Kemokai" CC: freebsd-questions@FreeBSD.ORG Subject: Re: DNS - Zone file References: <3542730D.ADBDE8B3@prodigy.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Saffa J. Kemokai wrote: > > Hello: > > I am looking for answers re DNS zone file. The file is created closely > after that located in FreeBSD Manual. The syntax looks OK since there > are no error messages now. My Up ISP was able to see the Zone file at > some point during the configuration. Suddenly, he can no longer see it. > Does any any has recommendation for me..? I really need to get this file > working even if you need some fees to help me here.. Unfortunately you didn't provide us with nearly enough information to even guess what the problem is. :) The first thing I would do is open two windows to the machine that the nameserver is on. You can do this at the console with virtual terminals or with X windows... whatever works for you. In one window I'd tail the log that named writes to. On a default system you'd do: tail -f /var/log/messages If you've moved your named log to a different location, use that filename instead. Next, I'd kill the nameserver and restart it. Then go to the other window and watch the messages you see in the log while the nameserver is starting. You should get some good hints as to what the problem is and where to look to solve it. If that doesn't fix you up and the zone file is short, post it to the list and I or someone will take a look at it and hopefully find your error. If you're not comfortable posting it to the list or it's very long, feel free to send it to me personally. DNS work is one of the things I do for a living, but if your problem is easy to see and fix (and most problems of this nature are, especially if it was working at one time) I won't charge you. If it's something that would take more time to fix than I'm comfortable with giving away I will contact you and we can negotiate terms. Finally, if you are doing serious DNS work where your time is valuable, I cannot recommend highly enough that you purchase the book "DNS and BIND, Second Edition" by Paul Albitz and Cricket Liu. It is published by O'Reilly and Associates and is THE book on DNS. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud designer and maintainer of the world's largest Internet *** Relay Chat server with 5,328 simultaneous connections. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message