Bonjour a tous,

je decouvre linux et ses serveurs depuis un mois maintenant pour le travail mais aussi par plaisir

mon boss m'a demander d'installer un serveur linux (mail, dns, ftp, www, php, sql) gere par PHP avec une interface local creer par moi lol

j'ai accepter surtout par defi car ce n'est pas vraiment mon domaine et je m'en rend de plus en plus compte depuis un mois lol

pour le moment j'utilise Proftpd que je gere via phpmyadmin, le serveur www - mysql - php marche bien que la fonction mail() de php ne passe pas mais bon je pense que c'est parce que j'essaye de passe par un smtp externe, je verai quand j'aurai installer le serveur de mail en local si cela marche.

par contre je bloque grave sur BIND9 je pense avoir une bonne config mais je ne comprends pas ce qui cloche

je vous met ici une petite desciption de la PME ou je bosse pour mieux comprendre

j'ai un réseau subdivisé en 7 sous réseaux.
192.168.1.0
192.168.2.0
192.168.3.0
192.168.4.0 --> c'est dans celui la qu'ens le serveur linux(apache, sql,samba,proftpd,pour le moment mais qui fera office aussi de DNS serveur et mailserveur.) adresse du serveur linux = 192.168.4.3 /24
192.168.5.0
192.168.6.0
192.168.7.0

/24

j'ai un routeur qui de sorti qui acquiere son adresse ip via dhcp mais j'ai une redirection no-ip.org du type xxx-xxx.no-ip.org

je vous met ici les divers fichier conf , log et test
si vous pouviez y jeter un coup d'oiel c'a m aiderai bcp

voice mon 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 " angelz-cuesmes.no-ip.org " {
        type master;
        file "/etc/bind/db.angel-ces.no-ip.org";
};

zone "4.168.192.in-addr.arpa" {
        type master;
        file "/etc/bind/db.angel-ces.no-ip.org.inv";
};

// 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";

db.angel-ces.no-ip.org

$TTL 3h
@       IN      SOA     ns.angel-ces.no-ip.org. hostmaster.angel-ces.no-ip.org. (
                                2007030701
                                8H
                                2H
                                1W
                                1D )

@       IN      NS      ns.angel-ces.no-ip.org.

@       IN      MX      10      mail.angel-ces.no-ip.org.

ns              IN      A       192.168.4.3
mail           IN      A       192.168.4.3
Serveur          IN      A       192.168.4.3
ftp             IN       A       192.168.4.3
www             IN       VNAME    Serveur

db.angel-ces.no-ip.org.inv

$TTL 3h
@       IN      SOA     ns.angel-ces.no-ip.org. hostmaster.angel-cues.no-ip.org. (
                                2007030701
                                8H
                                2H
                                1W
                                1D )

@       IN      NS      ns.angel-ces.no-ip.org.

@       IN      MX      10      mail.angel-ces.no-ip.org.

101             IN      PTR     ns.angel-ces.no-ip.org.
101             IN      PTR     mail.angel-ces.no-ip.org.
101             IN      PTR     Serveur.angel-ces.no-ip.org.
102             IN      PTR     ftp.angel-ces.no-ip.org.
103             IN      PTR     www. angel-ces.no-ip.org.

named.conf.options

ptions {
        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 {
                195.130.130.1;
         };

        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };

        // By default, name servers should only perform recursive domain
        // lookups for their direct clients.  If recursion is left open
        // to the entire Internet, your name server could be used to
        // perform distributed denial of service attacks against other
        // innocent computers.  For more information on DDoS recursion:
        // [cve.mitre.org]

        allow-recursion { localnets; };

        // If you have DNS clients on other subnets outside of your
        // server's "localnets", you can explicitly add their networks
        // without opening up your server to the Internet at large:
        // allow-recursion { localnets; 192.168.0.0/24; };

        // If your name server is only listening on 127.0.0.1, consider:
        // allow-recursion { 127.0.0.1; };
};

named.conf.local

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

maintenant qd jefais

sudo /etc/init.d/bind9 restart

j'ai ca

 * Stopping domain name service... bind
   ...done.
 * Starting domain name service... bind
   ...done.

et quand je fair

sudo sh -x /etc/init.d/bind9 restart

voici ce que cela donne

+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ OPTIONS=
+ RESOLVCONF=yes
+ test -f /etc/default/bind9
+ . /etc/default/bind9
+ OPTIONS=-u bind
+ RESOLVCONF=yes
+ test -x /usr/sbin/rndc
+ . /lib/lsb/init-functions
+ FANCYTTY=
+ [ -e /etc/lsb-base-logging.sh ]
+ . /etc/lsb-base-logging.sh
+ lsb_release -is
+ DISTRO=Ubuntu
+ /etc/init.d/bind9 stop
 * Stopping domain name service... bind
   ...done.
+ sleep 2
+ /etc/init.d/bind9 start
 * Starting domain name service... bind
   ...done.
+ exit 0

mais quand je fais

sudo tail -30 /var/log/syslog

j'obtient

May 13 14:10:32 serveur named[8793]: shutting down: flushing changes
May 13 14:10:32 serveur named[8793]: stopping command channel on 127.0.0.1#953
May 13 14:10:32 serveur named[8793]: stopping command channel on ::1#953
May 13 14:10:32 serveur named[8793]: no longer listening on ::#53
May 13 14:10:32 serveur named[8793]: no longer listening on 127.0.0.1#53
May 13 14:10:32 serveur named[8793]: no longer listening on 192.168.4.3#53
May 13 14:10:32 serveur named[8793]: exiting
May 13 14:10:34 serveur named[8859]: starting BIND 9.3.4 -u bind
May 13 14:10:34 serveur named[8859]: found 1 CPU, using 1 worker thread
May 13 14:10:34 serveur named[8859]: loading configuration from '/etc/bind/named.conf'
May 13 14:10:34 serveur named[8859]: listening on IPv6 interfaces, port 53
May 13 14:10:34 serveur named[8859]: listening on IPv4 interface lo, 127.0.0.1#53
May 13 14:10:34 serveur named[8859]: listening on IPv4 interface eth0, 192.168.4.3#53
May 13 14:10:34 serveur named[8859]: command channel listening on 127.0.0.1#953
May 13 14:10:34 serveur named[8859]: command channel listening on ::1#953
May 13 14:10:34 serveur named[8859]: zone 0.in-addr.arpa/IN: loaded serial 1
May 13 14:10:34 serveur named[8859]: zone 127.in-addr.arpa/IN: loaded serial 1
May 13 14:10:34 serveur named[8859]: dns_rdata_fromtext: /etc/bind/db.angel-ces.no-ip.org.inv:17: near 'angel-ces.no-ip.org.': extra input text
May 13 14:10:34 serveur named[8859]: zone 4.168.192.in-addr.arpa/IN: loading master file /etc/bind/db.angel-ces.no-ip.org.inv: extra input text
May 13 14:10:34 serveur named[8859]: zone 255.in-addr.arpa/IN: loaded serial 1
May 13 14:10:34 serveur named[8859]: zone localhost/IN: loaded serial 1
May 13 14:10:34 serveur named[8859]: /etc/bind/db.angel-ces.no-ip.org:11: \032angel-ces.no-ip.org\032: bad owner name (check-names)
May 13 14:10:34 serveur named[8859]: zone \032angel-ces.no-ip.org\032/IN: loading master file /etc/bind/db.angel-ces.no-ip.org: bad owner name (check-names)
May 13 14:10:34 serveur named[8859]: running
May 13 14:10:56 serveur ccsd[4074]: Unable to connect to cluster infrastructure after 4470 seconds. 
May 13 14:11:27 serveur ccsd[4074]: Unable to connect to cluster infrastructure after 4500 seconds. 
May 13 14:11:57 serveur ccsd[4074]: Unable to connect to cluster infrastructure after 4530 seconds. 
May 13 14:12:27 serveur ccsd[4074]: Unable to connect to cluster infrastructure after 4560 seconds. 
May 13 14:12:57 serveur ccsd[4074]: Unable to connect to cluster infrastructure after 4590 seconds. 
May 13 14:13:27 serveur ccsd[4074]: Unable to connect to cluster infrastructure after 4620 seconds.

ce qui me pousse a croire que cela ne marche pas

surtoutque si je fais

nslookup 192.168.4.3
(qui a l'adresse local du serveur)

j'ai

Server:         192.168.4.3
Address:        192.168.4.3#53

** server can't find 3.4.168.192.in-addr.arpa: SERVFAIL

ou si

nslookup ns.angel-ces.no-ip.org  
(qui est le nom du serveur)

j'ai

Server:         192.168.4.3
Address:        192.168.4.3#53

** server can't find ns.angel-ces.no-ip.org: NXDOMAIN

Voila je pense donc qu il y a un souci qlq part

j'espere vraiment que quelqu un pourra m'aider car ca fais 1 semaine que je suis dessus lol

merci d'avance

Poste le Monday 14 May 2007 17:10:23