Search Again: Re: QuickDNS logs From: Men & Mice Support Date: Thursday, April 12, 2001 Time: 2:19:44 pm There is no log analysis software for QuickDNS Pro's debug-level logs, which is the only level that logs all traffic. If you don't have Timbuktu access to the server, then the only way to gauge traffic without help from another application (firewall, router, etc.) is to turn on debug logging. If you do have Timbuktu access to the server, just log in and look at the statistics window. You can look at the log to determine when it last started up, so that will tell you the time frame that the stats represent. The window will tell you how many requests have been received, how many requests were answered from cache (cache includes your own domain files), how many requests have been sent, answers received, etc. If you had version 3, you could see all this (along with an indication of how long it's been up) remotely, using QuickDNS Pro Manager. Keep in mind that, if your router is reporting packets, an HTTP response will involve numerous packets. If your router is reporting bytes, there's no way to determine from QuickDNS how many bytes it's receiving and sending, other than to say that nearly all packets will be below 512 bytes (generally far below). ____________________________________________________________________ Chris Buxton Men & Mice cbuxton@menandmice.com We Make DNS Easy! At 10:08 AM -0400 4/12/01, ahclist wrote: >Chris & Co, > >Hey, I've a strange request here. I have a couple of our servers >colo'ed, running QuickDNS 2.2.1 and Webstar 4.2 on these beasties. >Our traffic is far higher than I would have expected from the logs >we can monitor effectively (http, mail and a horribly inaccurate ftp >log from webstar's plugin). Assuming the data from these combined >logs is within 20% of the actual traffic, I still cannot account for >nearly 80% of our traffic loads to the servers. The traffic is >measured from the router logs at the colo -- which unfortunately >cannot break down the traffic by port (oh, wouldn't that be sweet). > >Now, short of turning on the "thorough" setting in QDNS, is there an >"guess-timate" of how much network traffic a DNS server will see >over the course of the day? Is it relational or independent to the >number of domains (primary, secondary, or both) to which it is >authoritative? > >Any info would be wonderfully helpful in having us track this >craziness. We monitor our servers via an http hit every five >minutes. Our colo boxes are also monitored by the colo facility >every 30 seconds, and a couple of our customers separately monitor >their domains periodically -- all of this shows up in the http logs >-- and accounts for a negligible quantity of traffic. Would it be >beneficial to run thorough logs for 48 hours to gauge activity, or >would I end up with 100 Mb of data I wouldn't be able to analyze >without writing my own analyzer? (Is there a DNS log analyzer for >your product akin to FunnelWeb or Summary?). Obviously, this is a >financial issue for me otherwise I wouldn't be so curious. > >Thanks, > >paul vail >after hours

Messages In This Thread: QuickDNS logs by ahclist on Apr 12, 2001 at 7:11:51 am Re: QuickDNS logs by Men & Mice Support on Apr 12, 2001 at 2:19:44 pm