mammique wrote:
Bonjour,

je me casse les dents depuis deux jours non-stop pour migrer mon
ddns/dhcp hardware (Speedtouch Pro) vers mon serveur local (woody). Pour
le dhcp je n'ai e�t aucun probl�me, r�gl� en 15 mn (RTFM compris), en
revanche pour updater bind avec les noms de machines fra�chement
authentifi�es par dhcpd je suis ext�nu�, �a fait 2 jours que je suis
dessus �a ne veut rien savoir. Bind fonctionne, il sert correctement les
requ�tes DNS du net (forwarders {};), mais ne semble pas accepter les
mises � jour de dhcpd, je sais qu'il communiquent entre eux car selon la
config de named.conf j'ai un warning de dhcpd diff�rent ("timed out" ou
"not authorized"). De son c�t� bind ne dit rien, il communique bien avec
dhcpd mais ne m'informe m�me pas des requ�tes refus�es, du coup je ne
comprend pas ce qui cloche, j'ai pourtant remplis la section "logging"
de named.conf. Rien d'explicite sur le net ne m'a permis de r�soudre ce
probl�me, c'est pourquoi je jette ce Thread � la mer.

Tu as deux lignes ddns-update-style dans ton dhcpd.conf.
Essaie de d�placer ddns-domainname dans la partie subnet.
Si tu veux je peux t'envoyer mes fichiers en priv�.


mammique.





################################################################################
# Message de dhcpd lors d'une requ�te dhcp :
################################################################################
Mar 24 15:17:43 localhost dhcpd: DHCPRELEASE of 10.0.0.253 from
00:a0:cc:d8:3e:80 via eth0 (found)
Mar 24 15:17:43 localhost dhcpd: DHCPDISCOVER from 00:a0:cc:d8:3e:80 via
eth0
Mar 24 15:17:44 localhost dhcpd: DHCPOFFER on 10.0.0.253 to
00:a0:cc:d8:3e:80 via eth0
Mar 24 15:17:44 localhost dhcpd: DHCPDISCOVER from 00:a0:cc:d8:3e:80 via
eth0
Mar 24 15:17:44 localhost dhcpd: DHCPOFFER on 10.0.0.253 to
00:a0:cc:d8:3e:80 (PlasticBertrand) via eth0
Mar 24 15:17:44 localhost dhcpd: Unable to add forward map from
PlasticBertrand.industrie to 10.0.0.253: timed out
Mar 24 15:17:44 localhost dhcpd: DHCPREQUEST for 10.0.0.253 (10.0.0.254)
from 00:a0:cc:d8:3e:80 (PlasticBertrand) via eth0
Mar 24 15:17:44 localhost dhcpd: DHCPACK on 10.0.0.253 to
00:a0:cc:d8:3e:80 (PlasticBertrand) via eth0
################################################################################




################################################################################
# named.conf
################################################################################
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian for information on the
// structure of BIND configuration files in Debian, *BEFORE* you
customize
// this configuration file.
//
logging {
            channel update_debug {
                 file "/var/log/named_debug.log";
                 severity  debug 3;
                 print-category yes;
                 print-severity yes;
                 print-time     yes;
            };
            channel security_info    {
                 file "/var/log/named_info.log";
                 severity  info;
                 print-category yes;
                 print-severity yes;
                 print-time     yes;
            };
category packet { security_info; };
            category update { update_debug; };
            category security { security_info; };
            category default { default_syslog; default_debug; };
       };
options {
        directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
        // to talk to, you might need to uncomment the query-source
        // directive below.  Previous versions of BIND always asked
        // questions using port 53, but BIND 8.1 and later use an
unprivileged
        // port by default.
// query-source address * port 53; // If your ISP provided one or more IP addresses for stable
        // nameservers, you probably want to use them as forwarders.
        // Uncomment the following block, and insert the addresses
replacing
        // the all-0's placeholder.
forwarders {
                193.252.19.3;
        };
auth-nxdomain no; # conform to RFC1035 }; key "rndc-key" {
        algorithm hmac-md5;
        secret "XXXXXXXXXXXXXXXXXX";
};
controls {
        inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { rndc-key; };
};
view internal {
        match-clients { 10.0.0.0/24; };
        recursion yes;
// 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";
};
// add entries for other zones below here zone "moulive" {
        type master;
        file "/etc/bind/moulive.hosts";
        allow-update { key rndc-key; };
};
zone "0.0.10.in-addr.arpa" {
        type master;
        file "/etc/bind/moulive.hosts.rev";
        allow-update { key rndc-key; };
};
};
################################################################################




################################################################################
# rndc.conf
################################################################################
key "rndc-key" {
        algorithm hmac-md5;
        secret "XXXXXXXXXXXXXXXXXX";
};
options {
        default-key "rndc-key";
        default-server 127.0.0.1;
        default-port 953;
};
################################################################################





################################################################################
# dhcpd.conf
################################################################################
#
# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.4 2002/05/05 21:28:06 peloy Exp $
#
# The ddns-updates-style parameter controls whether or not the server
will
# attempt to do a DNS update when a lease is confirmed. We default to
the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
key "rndc-key" {
        algorithm hmac-md5;
        secret "XXXXXXXXXXXXXXXXXX";
};
ddns-update-style none; # option definitions common to all supported networks...
# option domain-name "example.org";
# option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
ddns-update-style interim;
        ignore client-updates;
        ddns-updates on;
        ddns-domainname "industrie";
        ddns-rev-domainname "in-addr.arpa";
authoritative;
subnet 10.0.0.0 netmask 255.255.255.0 {
        option routers 10.0.0.138;
        option domain-name "industrie";
        option domain-name-servers 10.0.0.254;
        range 10.0.0.0 10.0.0.254;
}
zone industrie. {
        primary 127.0.0.1;
        key rndc-key;
        }
zone 0.0.10.in-addr.arpa. {
        primary 127.0.0.1;
        key rndc-key;
        }
################################################################################


Répondre à