Forum général.général Bind ne marche pas

Posté par  .
Étiquettes : aucune
0
7
juil.
2006
Bonjour, SVP j'ai installé un serveur bind , je l'ai configuré mais le test ne marche pas, voila mes fichiers de conf, si vous avez une idée SVP sur la nature du probléme. Merci beaucoup

---------------------127.0.0.1.zone
$TTL 1W
@ IN SOA localhost. root.localhost. (
42 ; serial (d. adams)
2D ; refresh
4H ; retry
6W ; expiry
1W ) ; minimum

IN NS localhost.
1 IN PTR localhost.

----------------------- mon domaine : ast.fr
$TTL 4H
@ IN SOA localhost.ast.fr. root.localhost. (
2006070312 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D ; Minimum
)

@ IN NS 192.168.0.2


localhost IN A 127.0.0.1

------------------ localhost.zone

$TTL 1W
@ IN SOA @ root (
42 ; serial (d. adams)
2D ; refresh
4H ; retry
6W ; expiry
1W ) ; minimum

IN NS @
IN A 127.0.0.1

-------------------------0.168.192(reverse)

$TTL 4H
@ IN SOA localhost.ast.fr. root.localhost. (
2006070312 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D ; Minimum
)

@ IN NS 192.168.0.2
2.0.168.192.in-addr.arpa. IN PTR localhost.

--------------------named.conf

options {

# The directory statement defines the name server's working directory

directory "/var/lib/named";
pid-file "/var/run/named.pid";
# Write dump and statistics file to the log subdirectory. The
# pathenames are relative to the chroot jail.

dump-file "/var/log/named_dump.db";
statistics-file "/var/log/named.stats";

# The forwarders record contains a list of servers to which queries
# should be forwarded. Enable this line and modify the IP address to
# your provider's name server. Up to three servers may be listed.

#forwarders { 194.2.0.20; 194.2.0.50; };

# Enable the next entry to prefer usage of the name server declared in
# the forwarders section.

forward first;

# The listen-on record contains a list of local network interfaces to
# listen on. Optionally the port can be specified. Default is to
# listen on all interfaces found on your system. The default port is
# 53.

listen-on port 53 { 127.0.0.1; };

# The listen-on-v6 record enables or disables listening on IPv6
# interfaces. Allowed values are 'any' and 'none' or a list of
# addresses.

#listen-on-v6 { any; };

# The next three statements may be needed if a firewall stands between
# the local server and the internet.

#query-source 194.206.247.1 * port 53;
#transfer-source 194.204.247.1;
# notify-source * port 53;

# The allow-query record contains a list of networks or IP addresses
# to accept and deny queries from. The default is to allow queries
# from all hosts.

allow-query { internals; externals };

# If notify is set to yes (default), notify messages are sent to other
# name servers when the the zone data is changed. Instead of setting
# a global 'notify' statement in the 'options' section, a separate
# 'notify' can be added to each zone definition.

notify yes;
};

# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
# # Log queries to a file limited to a size of 100 MB.
# channel query_logging {
# file "/var/log/named_querylog"
# versions 3 size 100M;
# print-time yes; // timestamp log entries
# };
# category queries {
# query_logging;
# };
#
# # Or log this kind alternatively to syslog.
# channel syslog_queries {
# syslog user;
# severity info;
# };
# category queries { syslog_queries; };
#
# # Log general name server errors to syslog.
# channel syslog_errors {
# syslog user;
# severity error;
# };
# category default { syslog_errors; };
#
# # Don't log lame server messages.
# category lame-servers { null; };
#};


# Logging section
logging {
channel security_channel {
file "/var/log/bind/security.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};

channel default_channel {
file "/var/log/bind/default.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};

channel xfer-in_channel {
file "/var/log/bind/xfer-in.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};

channel xfer-out_channel {
file "/var/log/bind/xfer-out.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};

channel update_channel {
file "/var/log/bind/update.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};

channel notify_channel {
file "/var/log/bind/notify.log" versions 4 size 10m;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
category security { security_channel; };
category default { default_channel; };
category xfer-in { xfer-in_channel; };
category xfer-out { xfer-out_channel; };
category notify { notify_channel; };
category update { update_channel; };
category lame-servers { null; };
category delegation-only { "null" ; };
};



# The following zone definitions don't need any modification. The first one
# is the definition of the root name servers. The second one defines
# localhost while the third defines the reverse lookup for localhost.

zone "." in {
type hint;
file "root.hint";
};

zone "localhost" in {
type master;
file "localhost.zone";
};

zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0";
};

zone "ast.fr" {
type master;
notify yes;
file "db.ast.fr";
# allow-transfer { localhost; 192.168.0.2; };

zone "2.168.192.in-addr.arpa" in {
type master;
file "db.192.168.0.2";
};

voila ce que ca donne pour nslookup :

linux:~ # nslookup
> ast.fr
Server: 192.168.0.2
Address: 192.168.0.2#53

** server can't find ast.fr: SERVFAIL
> 192.168.0.2
Server: 192.168.0.2.2
Address: 192.168.0.2#53

** server can't find 192.168.0.2.in-addr.arpa: SERVFAIL
> 127.0.0.1
Server: 192.168.0.2
Address: 192.168.0.2#53

1.0.0.127.in-addr.arpa name = localhost.
> localhost
Server: 192.168.0.2
Address: 192.168.0.2#53

Name: localhost
Address: 127.0.0.1
>

Merci
  • # Les logs, vérification de la conf...

    Posté par  (site web personnel) . Évalué à 1.

    Et les logs disent quoi au lancement de bind ?

    named-checkconf et named-checkzone sont contents également ?
  • # forward

    Posté par  . Évalué à 1.

    Un premier truc qui me choque c'est le forward first sans forwarders déclarés.

    Sinon comme dit plus haut sors nous ton log ca sera plus facile de te donner un coup de main.
    • [^] # Re: forward

      Posté par  . Évalué à 1.

      Merci pour vos réponses.

      J'ai mis le forwarders en commentaire et j'ai oublie de faire la meme chose pour le forwarder first, dés que mon serveur va marcher , je décommente les 2 parce que je les aurai besoin.

      J'ai oublié de vous dire que j'ai changé le chemin par defaut du fichier named.conf , il était dans /etc/named.conf et moi je l'ai mis dans /etc/bind/named.conf .

      la premier ligne des logs me montre que le systéme load la config à partir le fichier '/etc/named.conf, donc je pense que c'est ça le probléme, mais je sais pas quel fichier je dois éditer pour changer le chemin. Avez vous ube idée sur ce fichier (je suis encore nouveau en linux :) :))
      voila les logs :

      linux:~ # tail -f /var/log/messages
      Jul 7 15:19:16 linux named[9786]: loading configuration from '/etc/named.conf'
      Jul 7 15:19:16 linux named[9786]: listening on IPv6 interfaces, port 53
      Jul 7 15:19:16 linux named[9786]: listening on IPv4 interface lo, 127.0.0.1#53
      Jul 7 15:19:16 linux named[9786]: listening on IPv4 interface eth0, 192.168.0.2#53
      Jul 7 15:19:16 linux named[9786]: command channel listening on 127.0.0.1#953
      Jul 7 15:19:16 linux named[9786]: command channel listening on ::1#953
      Jul 7 15:19:16 linux named[9786]: zone 0.0.127.in-addr.arpa/IN: loaded serial 42
      Jul 7 15:19:16 linux named[9786]: zone localhost/IN: loaded serial 42
      Jul 7 15:19:16 linux named[9786]: running
      Jul 7 15:20:38 linux su: (to root) abarouat on /dev/pts/0
      • [^] # Re: forward

        Posté par  (site web personnel) . Évalué à 1.

        Au pire fais un ln -s /etc/bind/named.conf /etc/named.conf

        Ca fera un lien symbolique (un raccourci quoi) de ton fichier dans /etc/bind/ vers /etc .

Suivre le flux des commentaires

Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.