Hello,
Finally solved. Thank to all of you, and specially Holger Honert.
I'm using bind with chroot, so there was some different stuff in where to put
the logs.
Also there was a dot missing on my PTR.
Now I have this on my named.conf.options to let me have underscores:
check-names master ignore;
check-names slave ignore;
And I have this on my named.conf
logging {
channel named_log {
file "/var/log/named.log" versions 5 size 5m;
severity dynamic;
print-category yes;
print-severity yes;
print-time yes;
};
channel security_log {
file "/var/log/security.log" versions 5 size 5m;
severity debug ;
print-category yes;
print-severity yes;
print-time yes;
};
channel update_log {
file "/var/log/update.log" versions 5 size 5m;
severity debug ;
print-category yes;
print-severity yes;
print-time yes;
};
channel notify_log {
file "/var/log/notify.log" versions 5 size 5m;
severity debug ;
print-category yes;
print-severity yes;
print-time yes;
};
channel query_log {
file "/var/log/query.log" versions 10 size 5m;
severity debug ;
print-category yes;
print-severity yes;
print-time yes;
};
category default {named_log; };
category security {security_log; };
category update {update_log; };
category update-security {update_log; };
category notify {notify_log; };
category queries {query_log; };
category lame-servers { null; };
};
Thanks to all of you.
Joan Marc Riera Duocastella
Barcelona Media - Centre d'Innovació
Av. Diagonal, 177, planta 9 08018 - BARCELONA
Telèfon +34 93 238 14 00 Fax +34 93 309 31 88
www.barcelonamedia.org
-Mensaje original-
De: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org]
En nombre de Kevin Darcy
Enviado el: jueves, 05 de noviembre de 2009 18:05
Para: bind-users@lists.isc.org
Asunto: Re: ** server can't find barcelonamedia.org.barcelonamedia.org: SERVFAIL
"bind9" script: the "status" operand basically just passes back the
results of a "status_of_proc" call. status_of_proc appears to be a
Debian-ism, I can't easily find any info on it, but presumably there's
something misconfigured on your system, so that status_of_proc can't
find the "named" process. The "force-reload" operand, in contrast, uses
rndc, and that appears to be working fine. Talk to a Debian expert about
what might be wrong with status_of_proc.
"named.conf": there's nothing about logging in that named.conf, and the
zone definitions are totally generic (hints file, localhost,
127.in-addr.arpa, 0.in-addr.arpa and 255.in-addr.arpa). However, there
are a couple of subsidiary config files "include"d into this one --
named.conf.options (which might potentially contain your logging
configuration) and named.conf.local (which might contain zone definitions).
By the way, did you follow the advice in this comment:
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
?
- Kevin
Marc Riera wrote:
> Hello,
>
> Thanks for your repply, still don't have any idea about where the logs should
> be.
>
> I attatch my /etc/init.d/bind9 because of the strange behavior.
> Also attatch my /etc/bind/named.conf to see if the logs should be somewhere.
>
>
> I've already checked if there is something declared about logs in the config
> files with this result:
> FBMNS01:/etc/bind# egrep log *
> db.barcelonamedia.org:blogbmIN A 84.88.79.133
> db.barcelonamedia.org:blogbm2 IN A 84.88.79.142
>
>
> Thank you.
>
>
>
> Joan Marc Riera Duocastella
> Barcelona Media - Centre d'Innovació
> Av. Diagonal, 177, planta 9 08018 - BARCELONA
> Telèfon +34 93 238 14 00 Fax +34 93 309 31 88
> www.barcelonamedia.org
>
> -Mensaje original-
> De: bind-users-boun...@lists.isc.org
> [mailto:bind-users-boun...@lists.isc.org] En nombre de Kevin Darcy
> Enviado el: miércoles, 04 de noviembre de 2009 19:15
> Para: bind-users@lists.isc.org
> Asunto: Re: ** server can't find barcelonamedia.org.barcelonamedia.org:
> SERVFAIL
>
> a) without knowing the contents of your named.conf, it is difficult or
> impossible to tell why the logs might not exist where you think they
> should (it is somewhat unusual for logs to be written to a ${CHROOT}/dev
> subdirectory, is it not? I would normally expect to see only
