Tu ne verras rien du tout tant que tu n auras pas mis la logging section
dans
named.conf :
logging {
# category default { null; };
category default { default_syslog;default_debug; };
category lame-servers { null; };
category cname { null; };
};
Ci joint un named.conf qui marche !
Le dim 02/02/2003 � 10:59, S�bastien Lardi�re a �crit :
> On Sat, 01 Feb 2003 20:56:46 +0100
> S�bastien GALLET <[EMAIL PROTECTED]> racontait :
>
> > >
> > V�rifie ton named.conf, il manque la section crontrol (voir mon fichier
> > de conf). Je suis pas sur que ce soit indispensable mais ...
> > rndc fonctionne (rndc status)??? sinon modifie rndc.conf pour inclure ta cl�
>
> debian:/var/log# rndc status
> number of zones: 8
> debug level: 0
> xfers running: 0
> xfers deferred: 0
> soa queries in progress: 0
> query logging is OFF
> server is up and running
>
> apr�s avoir ajouter la section control dans named.conf et cr�e un rndc.conf
> avec la cl�. Avant, �a marchait aussi, c-a-d sans la section control dans
> named.conf, rndc n'a pas l'air d'avoir besoin de rndc.conf, puisqu'il n'en
> avait pas et rndc status me faisait la m�me r�ponse que ci-dessus.
>
> >
> > Modifie ton dhcpd.conf
> > Mets les param�tres
> > ddns-rev-domainname "in-addr.arpa.";
> > ddns-updates on;
> > ddns-domainname "seb.org.";
> > deny client-updates;
> > dans la d�finition de ta zone plut�t que la configuration globale
>
> Ok,
>
> >
> > >J'ai test� avec un client Debian et W2kPro, et m�me r�sultat, rien ne se
> > >passe.
> > >
> > >Je n'ai m�me pas de message d'erreur dans les logs, en fait, comme si
> > >Dhcpd ignorait tout simplement ma configuration. J'ai v�rifi� en faisant
> > >des fautes de syntaxe, il rale, donc il va bien lire le fichier.
> > >
> > Tu devrais avoir des messages dans /var/log/daemon pour dhcp
>
> je n'ai pas de fichier daemon, mais un daemon.log qui ne cause pas du tout de
> dhcp, a priori tout est dans syslog
>
> >
> > et dans /var/log/dns-security.log pour les mise � jour dns
>
> et toujours rien dans ce fichier. Rien a faire, ca veut pas.
>
> --
> S�bastien
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
/* sample configuration file for BIND 8.1 or later
* should be installed as /etc/named.conf
*
* Author: Florian La Roche
*/
#
# overall options of the server
#
options {
directory "/var/named";
# the default is to fail, if the master file is not correct
check-names master warn;
pid-file "/var/run/named.pid";
statistics-interval 0;
cleaning-interval 720;
datasize default;
stacksize default;
coresize default;
files unlimited;
recursion yes;
multiple-cnames no; // if yes, then a name my have more
// than one CNAME RR. This use
// is non-standard and is not
// recommended, but it is available
// because previous releases supported
// it and it was used by large sites
// for load balancing.
# the default is to ask the forwarders and if they fail
# try to find the answer yourself, this will only ask the forwarders
#forward only;
# list of DNS servers to ask
#forwarders {
# 192.168.0.10;
# 192.168.0.20;
# 192.168.0.30;
#};
# the default is to listen on port 53 on all available interfaces
# you can also give a detailed list:
#listen-on { 5.6.7.8; };
#listen-on port 1234 { !1.2.3.4; 1.2/16; };
};
#
# do not be verbose about these problems...
#
logging {
# category default { null; };
category default { default_syslog;default_debug; };
category lame-servers { null; };
category cname { null; };
};
#
# predefined access control lists (acl):
# "any" allows all hosts
# "none" denies all hosts
# "localhost" allows the IP adresses of all interfaces of the system
# "localnets" allows any host on a network of the local interfaces
#
# defining an additional ACL:
#acl can_download { 192.168.0.17; 192.168.0.18; };
#
# The server statement defines the characteristics to be associated with
# a remote name server.
#
# Marking a server as bogus will prevent queries to that server.
#server 192.168.0.128 { bogus yes; }
# If the other name server has also BIND 8.1 or newer installed, you
# can allow compacter zone transfers with this statement.
#server 192.168.0.128 { transfer-format many-answers; }
key DHCP_UPDATER {
algorithm HMAC-MD5.SIG-ALG.REG.INT;
secret iKzPTrUyA47iyKAOGE3gnQ==;
}
zone "." IN {
type hint;
file "root.hint";
};
zone "localhost" IN {
type master;
file "localhost.zone";
check-names fail;
allow-update { 192.9.9.238; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "127.0.0.zone";
allow-update { 127.0.0.1; };
};
# We should change the zone name to 'localdomain'
zone "mydomain.com" IN {
type master;
file "localdomain.zone";
# by default, any host can receive zone transfers
#allow-transfer { any; };
notify yes;
allow-update { 192.9.9.238;127.0.0.1;key DHCP_UPDATER; };
};
zone "9.9.192.in-addr.arpa" IN {
type master;
file "192.9.9.zone";
notify yes;
allow-update { 192.9.9.238;127.0.0.1; key DHCP_UPDATER;};
};
#
# a slave zone
#
#zone "isc.org" IN {
# type slave;
# file "slave/db.isc.org";
# masters { 192.168.0.128; };
#};
