[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bind 9 logging
- To: Openbsd Misc Mailing List <misc@openbsd.org>
- Subject: Re: Bind 9 logging
- From: Martin Schröder <martin@oneiros.de>
- Date: Tue, 2 Nov 2004 11:46:30 +0100
- Content-Disposition: inline
- Mail-Followup-To: Openbsd Misc Mailing List <misc@openbsd.org>
- References: <4186C2D3.8090900@ij.net>
- User-Agent: Mutt/1.4.2i
On 2004-11-01 18:12:19 -0500, paddy wrote:
> I have spent the last week learning DNS re: Bind 9. I have found some
> excellent documentation.
>
> "Introduction to DNS -including caching nameservers
> (http://www.aei.ca/~pmatulis/pub.obsd_dns.html
404
> and the most understandable Unix document which I have EVER come across
> DNS for Rocket Scientist
>
> http://www.zytrax.com/books/dns/?pf=yes.
Nice. :-)
RTFM: http://www.bind9.net/Bv9ARM.html
> The problem I have after searching the Internet, endless documentation,
> etc; is how does a chroot process do logging? Specifically, Openbsd
> Bind 9 logging from a chroot jail, step by step.
bind logs to a copy of /dev/log and syslog has to listen to it.
> There is lots of talk about this but noone explains the steps needed to
> create the Unix socket for syslog to operate and where are these files
> going to be located so a person can read them and find out how the
> program is operating, i.e. debug.
>
> Are there archives at any other address than The primates at monkey.org?
Check out bind-users :-)
Best regards
Martin
--
Martin Schröder, ms@artcom-gmbh.de
ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany
Voice +49 421 20419-44 / Fax +49 421 20419-10
http://www.artcom-gmbh.de