DNS keeps failing

Re: DNS keeps failing

From:

Date:

Time:

At 2:37 PM -0400 10/1/04, Steve Murphy wrote:
>Syslog does not seem to be entering any info into the message file
>other than BIND restarts. I have BIND chrooted, does this cause
>issues with what the system is able to log?

No. It simply means that the location of the QuickDNS Log channel's
output file is somewhere inside the jail. Be sure that QuickDNS
Remote is also running inside the same jail as named.

>I turned all the logging options on in the manager and nothing is
>showing up. Any ideas?

That doesn't surprise me. What are you expecting to see? It could
simply be that named hasn't had occasion to log anything since you
adjusted the logging settings.

Note that, when named crashes, it may not log anything at all. That's
just the nature of a crash - it's caused by something the programmers
didn't expect.

You may want to ask about this problem on the Fedora users mailing
list. (I'm confident there is one.) Other users may be having the
same problem, and they may have some explanation or even a solution
for it.

Chris Buxton
Men & Mice - Making DNS Easy
Customer Service and Sales Engineer

>-----Original Message-----
>From: quickdns-talk@lists.menandmice.com
>[mailto:quickdns-talk@lists.menandmice.com]On Behalf Of Men & Mice
>Support
>Sent: Friday, October 01, 2004 1:12 PM
>To: QuickDNS Talk
>Subject: Re: DNS keeps failing
>
>
>Hello Steve,
>
>QuickDNS by default sets up two logging channels. (If you set up any
>before installing QuickDNS, they are preserved.) The first is the
>QuickDNS Log, which is stored in a file in the named data directory
>(e.g. /var/named on some systems). The file name is quickdns.log. You
>can view this log in QuickDNS Manager by selecting the server in the
>Manager window and clicking on the Log button. (There are also menu
>items in both the Server menu and the contextual menu.)
>
>The second logging channel is the System Log, which is logged to
>syslogd. On Linux, the main syslogd log file is usually
>/var/log/messages - look for the named pid, or the string 'named',
>using grep. For example, since each log message is usually logged
>with the process name followed by the pid in square brackets:
>
>grep 'named\[' /var/log/messages
>
>Note that you can set what gets logged to each of these two channels,
>as well as any other channel, in QuickDNS Manager, in the server's
>Options window. Go to the Logging pane, select a channel in the
>drop-down menu at the top, and set the options (logging severity
>level and categories to be logged). Note that both (all) channels get
>logging messages, regardless of which channel is selected in the
>options window.
>
>Chris Buxton
>Men & Mice - Making DNS Easy
>Customer Service and Sales Engineer
>
>At 10:27 AM -0400 10/1/04, Steve Murphy wrote:
>>My primary NS server runs for about a day then crashes. I am running
>>BIND 9 on Fedora Core 2. The usual BIND error log is not in /var/log
>>where are the error logs when using QuickDNS?
>>
>>Steve

Sales:
888/4-DPOINT

Support:
858/452-3696