Logging Response Results

Stefan Certic stefan at routotelecom.com
Thu Jun 23 21:28:39 UTC 2011

It is Enum server, and logging is taking care of billing process.

Flow is going something like this:

- Accept Query
- Write QueryLog through Syslog
- Syslog do an insert into database.
- Respond to query by asking forwarder or through local master zone
(Everything fine till now)
- Log response sent to client through syslog ???
- Match initial query and update results (will deppend on previous step).

Hope you get the clear picture now.


On Thursday, June 23, 2011 10:42:19 pm Chuck Swiger wrote:
> On Jun 23, 2011, at 1:27 PM, Stefan Certic wrote:
> > Thanks Chuck
> > 
> > Yes, that would be a solution, but i need logs processed through syslog
> > and stored into database (matching the initial query from query log).
> Why do you need to send this information via syslog to a database?
> > Pharsing tcpdump is not going to be suitable for highly loaded system. I
> > was more looking for a solution to log responses same way queryes are
> > logged.
> Parsing tcpdump doesn't constitute much work; I've got scripts which deal
> with NTP traffic at 500 - 2000+ requests per second without consuming much
> resources...although monitoring NTP takes noticeably more work than ntpd
> itself needs to provide time.
> It's the other requirements being added which strike me as heavy-weight.
> Regards,

Stefan Certic

48 Charlotte Street
London, W1T 2NS
United Kingdom
GSMA Associate Member

Switchboard +44 (0) 870 231 7777 
Fax + 44 (0) 870 231 7775

Email  : stefan at routotelecom.com
MSN ID : stefan at routotelecom.com

This email contains information provided by Routo Telecommunications
Ltd, which may be privileged or confidential. It is meant only for the
individual(s) or entity named above. If you are not the intended
recipient, note that disclosing, copying, distributing or using this
information is prohibited. If you have received this email in error,
please let me know immediately on the email address above.

Routo Telecommunications Ltd may not be held responsible for the
content of this email as it may reflect the personal view of the
sender and not that of the company.

Internet communications cannot be guaranteed to be timely, secure,
error or virus-free. The sender does not accept liability for any
errors or omissions.

We monitor our email system and may record your emails.

Routo Telecommunications Ltd Registration Number 04546322 has its
principal place of business at 48 Charlotte Street, London, W1T 2NS,
United Kingdom.

More information about the bind-users mailing list