Bonjour,
J’ai actuellement un soucis avec bind je ne peux pas le redamarrer et j’ai le message suivant :
Stopping domain name service…: bindrndc: connect failed: 127.0.0.1#953: connection refused
failed!
Starting domain name service…: bind failed!
Merci de votre aide.
Que contient /var/log/syslog à propos de named ?
May 20 14:11:39 vmdebian named[2683]: starting BIND 9.3.4 -u bind
May 20 14:11:39 vmdebian named[2683]: found 1 CPU, using 1 worker thread
May 20 14:11:39 vmdebian named[2683]: loading configuration from '/etc/bind/named.conf’
May 20 14:11:39 vmdebian named[2683]: /etc/bind/named.conf:57: unknown option 'par’
May 20 14:11:39 vmdebian named[2683]: loading configuration: failure
May 20 14:11:39 vmdebian named[2683]: exiting (due to fatal error)
voicy la structure de mon michier named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// 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.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
include “/etc/bind/named.conf.options”;
// prime the server with knowledge of the root servers
zone “.” {
type hint;
file “/etc/bind/db.root”;
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone “localhost” {
type master;
file “/etc/bind/db.local”;
};
zone “127.in-addr.arpa” {
type master;
file “/etc/bind/db.127”;
};
zone “0.in-addr.arpa” {
type master;
file “/etc/bind/db.0”;
};
zone “255.in-addr.arpa” {
type master;
file “/etc/bind/db.255”;
};
// zone “com” { type delegation-only; };
// zone “net” { type delegation-only; };
// From the release notes:
// Because many of our users are uncomfortable receiving undelegated answers
// from root or top level domains, other than a few for whom that behaviour
// has been trusted and expected for quite some length of time, we have now
// introduced the “root-delegations-only” feature which applies delegation-only
// logic to all top level domains, and to the root domain. An exception list
// should be specified, including “MUSEUM” and “DE”, and any other top level
// domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { “DE”; “MUSEUM”; };
include “/etc/bind/named.conf.local”;
// Configurer le canal de communication pour adminsistrer BIND9 avec rndc
// Par défaut, la clef est située dans le fichier rndc.key et utiliser
par
// rndc et bind9 sur localhost
controls {
inet 127.0.0.1 port 53 allow { 127.0.0.1; };
// Configurer le canal de communication pour adminsistrer BIND9 avec rndc
// Par défaut, la clef est située dans le fichier rndc.key et utiliser
par
// rndc et bind9 sur localhostOn dirait que l’erreur vient du mot “par” du commentaire qui s’est retrouvé rejeté en début de ligne par un retour chariot intempestif.
[EDIT] Je vois que le port 53 est défini comme port d’administration dans la déclaration controls. Or le port 53 sert normalement à recevoir les requêtes DNS. Le port d’administration par défaut est 953.
Après modifs voila mon syslog
May 20 15:06:10 vmdebian named[3032]: loading configuration from '/etc/bind/named.conf’
May 20 15:06:10 vmdebian named[3032]: command channel listening on 127.0.0.1#953
May 20 15:06:14 vmdebian named[3032]: shutting down
May 20 15:06:14 vmdebian named[3032]: stopping command channel on 127.0.0.1#953
May 20 15:06:14 vmdebian named[3032]: no longer listening on ::#53
May 20 15:06:14 vmdebian named[3032]: no longer listening on 127.0.0.1#53
May 20 15:06:14 vmdebian named[3032]: no longer listening on 192.168.0.15#53
May 20 15:06:14 vmdebian named[3032]: exiting
May 20 15:06:17 vmdebian named[3068]: starting BIND 9.3.4 -c /etc/bind/named.conf
May 20 15:06:17 vmdebian named[3068]: found 1 CPU, using 1 worker thread
May 20 15:06:17 vmdebian named[3068]: loading configuration from '/etc/bind/named.conf’
May 20 15:06:17 vmdebian named[3068]: listening on IPv6 interfaces, port 53
May 20 15:06:17 vmdebian named[3068]: listening on IPv4 interface lo, 127.0.0.1#53
May 20 15:06:17 vmdebian named[3068]: listening on IPv4 interface eth0, 192.168.0.15#53
May 20 15:06:17 vmdebian named[3068]: none:0: open: /etc/bind/rndc.key: permission denied
May 20 15:06:17 vmdebian named[3068]: /etc/bind/named.conf:63: couldn’t install keys for command channel 127.0.0.1#953: permission denied
May 20 15:06:17 vmdebian named[3068]: /etc/bind/named.conf:63: couldn’t add command channel 127.0.0.1#953: permission denied
May 20 15:06:17 vmdebian named[3068]: zone 0.in-addr.arpa/IN: loaded serial 1
May 20 15:06:17 vmdebian named[3068]: zone 127.in-addr.arpa/IN: loaded serial 1
May 20 15:06:17 vmdebian named[3068]: zone 255.in-addr.arpa/IN: loaded serial 1
May 20 15:06:17 vmdebian named[3068]: zone localhost/IN: loaded serial 1
May 20 15:06:17 vmdebian named[3068]: zone ophiuchhus/IN: loaded serial 1211232926
May 20 15:06:17 vmdebian named[3068]: running
Après quelques modifs …;
May 20 15:31:36 vmdebian named[3588]: starting BIND 9.3.4 -c /etc/bind/named.conf
May 20 15:31:36 vmdebian named[3588]: found 1 CPU, using 1 worker thread
May 20 15:31:36 vmdebian named[3588]: loading configuration from '/etc/bind/named.conf’
May 20 15:31:36 vmdebian named[3588]: listening on IPv6 interfaces, port 53
May 20 15:31:36 vmdebian named[3588]: listening on IPv4 interface lo, 127.0.0.1#53
May 20 15:31:36 vmdebian named[3588]: listening on IPv4 interface eth0, 192.168.0.15#53
May 20 15:31:36 vmdebian named[3588]: command channel listening on 127.0.0.1#953
May 20 15:31:36 vmdebian named[3588]: zone 0.in-addr.arpa/IN: loaded serial 1
May 20 15:31:36 vmdebian named[3588]: zone 127.in-addr.arpa/IN: loaded serial 1
May 20 15:31:36 vmdebian named[3588]: zone 255.in-addr.arpa/IN: loaded serial 1
May 20 15:31:36 vmdebian named[3588]: zone localhost/IN: loaded serial 1
May 20 15:31:36 vmdebian named[3588]: zone ophiuchhus/IN: loaded serial 1211232926
May 20 15:31:36 vmdebian named[3588]: running
