A voir également:
- Configuration DNS
- Changer dns - Guide
- Ethernet n'a pas de configuration ip valide - Guide
- Dns gratuit - Guide
- Panneau de configuration - Guide
- Configuration chromecast - Guide
2 réponses
Droopy_
Messages postés
248
Date d'inscription
dimanche 16 novembre 2008
Statut
Membre
Dernière intervention
17 janvier 2009
25
20 nov. 2008 à 03:01
20 nov. 2008 à 03:01
Peux-tu poster ton named.conf ?
Le fichier named.root.hints est la liste des serveurs racine pour faire une recherche à partir de la racine d'internet.
Le fichier named.root.hints est la liste des serveurs racine pour faire une recherche à partir de la racine d'internet.
20 nov. 2008 à 10:40
//
// Sample named.conf BIND DNS server 'named' configuration file
// for the Red Hat BIND distribution.
//
// See the BIND Administrator's Reference Manual (ARM) for details, in:
// file:///usr/share/doc/bind-*/arm/Bv9ARM.html
// Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
// its manual.
//
options
{
/* make named use port 53 for the source of all queries, to allow
* firewalls to block all ports except 53:
*/
query-source port 53;
query-source-v6 port 53;
// Put files that named is allowed to write in the data/ directory:
directory "/var/named"; // the default
dump-file "data/cache_dump.db";
statistics-file "data/named_stats.txt";
memstatistics-file "data/named_mem_stats.txt";
};
logging
{
/* If you want to enable debugging, eg. using the 'rndc trace' command,
* named will try to write the 'named.run' file in the $directory (/var/named).
* By default, SELinux policy does not allow named to modify the /var/named directory,
* so put the default debug log file in data/ :
*/
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
//
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
//
view "localhost_resolver"
{
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
* If all you want is a caching-only nameserver, then you need only define this view:
*/
match-clients { localhost; };
match-destinations { localhost; };
recursion yes;
# all views must contain the root hints zone:
include "/etc/named.root.hints";
/* these are zones that contain definitions for all the localhost
* names and addresses, as recommended in RFC1912 - these names should
* ONLY be served to localhost clients:
*/
include "/etc/named.rfc1912.zones";
};
view "internal"
{
/* This view will contain zones you want to serve only to "internal" clients
that connect via your directly attached LAN interfaces - "localnets" .
*/
match-clients { localnets; };
match-destinations { localnets; };
recursion yes;
// all views must contain the root hints zone:
include "/etc/named.root.hints";
// include "named.rfc1912.zones";
// you should not serve your rfc1912 names to non-localhost clients.
// These are your "authoritative" internal zones, and would probably
// also be included in the "localhost_resolver" view above :
zone "my.internal.zone" {
type master;
file "my.internal.zone.db";
};
zone "my.slave.internal.zone" {
type slave;
file "slaves/my.slave.internal.zone.db";
masters { /* put master nameserver IPs here */ 127.0.0.1; } ;
// put slave zones in the slaves/ directory so named can update them
};
zone "my.ddns.internal.zone" {
type master;
allow-update { key ddns_key; };
file "slaves/my.ddns.internal.zone.db";
// put dynamically updateable zones in the slaves/ directory so named can update them
};
};
zone "aster.sn" IN {
type master;
allow-update { none; };
file "aster.zone";
};
key ddns_key
{
algorithm hmac-md5;
secret "use /usr/sbin/dns-keygen to generate TSIG keys";
};
view "external"
{
/* This view will contain zones you want to serve only to "external" clients
* that have addresses that are not on your directly attached LAN interface subnets:
*/
match-clients { !localnets; !localhost; };
match-destinations { !localnets; !localhost; };
recursion no;
// you'd probably want to deny recursion to external clients, so you don't
// end up providing free DNS service to all takers
// all views must contain the root hints zone:
include "/etc/named.root.hints";
// These are your "authoritative" external zones, and would probably
// contain entries for just your web and mail servers:
zone "my.external.zone" {
type master;
file "my.external.zone.db";
};
};
132,1 Bas
1,1 Haut
20 nov. 2008 à 22:38
Tout au long du fichier tu as des includes vers des fichiers dans /etc
Range tous ces fichiers dans ton répertoire (en général /var/named),
puis change les includes de façon appropriée.
Dans l'install, quelque part, tu dois avoir le fichier hints ( named.root.hints )
il faut aussi que ce fichier soit correctement déclaré.
24 nov. 2008 à 15:39
Maintenant j'ai réinstallé mon OS mais c'est toujours la mem distribution (fc6);dans le rep /etc/ j'ai les fichiers named.caching_nameserver.conf
[root@aster-server ~]# vim /etc/named.caching-nameserver.conf
//
// named.caching-nameserver.conf
//
// Provided by Red Hat caching-nameserver package to configure the
// ISC BIND named(8) DNS server as a caching only nameserver
// (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// DO NOT EDIT THIS FILE - use system-config-bind or an editor
// to create named.conf - edits to this file will be lost on
// caching-nameserver package upgrade.
//
options {
listen-on port 53 { 127.0.0.1; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
query-source port 53;
query-source-v6 port 53;
allow-query { localhost; };
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
view localhost_resolver {
match-clients { localhost; };
match-destinations { localhost; };
recursion yes;
include "/etc/named.rfc1912.zones";
};
et named.rfc1912.zones
[root@aster-server ~]# vim /etc/named.rfc1912.zones
// named.rfc1912.zones:
//
// Provided by Red Hat caching-nameserver package
//
// ISC BIND named zone configuration for zones recommended by
// RFC 1912 section 4.1 : localhost TLDs and address zones
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
zone "." IN {
type hint;
file "named.ca";
};
zone "localdomain" IN {
type master;
file "localdomain.zone";
allow-update { none; };
};
zone "aster.com" IN {
type master;
file "aster.com.zone";
allow-update { none; };
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN {
type master;
file "named.ip6.local";
allow-update { none; };
};
zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};
zone "0.in-addr.arpa" IN {
type master;
file "named.zero";
allow-update { none; };
};
mon domaine s'appelle aster.com
voici mon fichier aster.com.zone
$TTL 86400
aster.com. IN SOA aster-server.aster.com. root.aster.com. (
42 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
aster.com. IN NS aster-server.aster.com.
aster-server.aster.com. IN A 127.0.0.1
www.aster.com. IN CNAME aster-server.aster.com.
aster.com. IN MX 1 aster-server.aster.com.
~
~
~
~
~
~
~
~
~
~
Puis je lance les commandes suivantes:
[root@aster-server ~]# /etc/init.d/named restart
Arrêt de named : [ OK ]
Démarrage de named : [ OK ]
[root@aster-server ~]# nslookup
> aster.com
Server: 127.0.0.1
Address: 127.0.0.1#53
** server can't find aster.com: SERVFAIL
il n'affiche pas l'enregistrement MX ni le nom complet de la machine et pourtant je l'ai bien précisé dans le fichier aster.com.zone .
Maintenant je travaille en local c'est à dire j'utilise l'@ 127.0.0.1 et ma machine s'appelle aster-server.Si vous pouvez me repondre le plus vite que possible car mon principal but c'est de mettre en place un serveur de messagerie
26 nov. 2008 à 03:03
Donc tu définis :
un nameserver pour aster.com
une IP 127.0.0.1 pour aster-server.aster.com
un cname vers aster-server.aster.com pour www.aster.com
et un MX vers aster-server.aster.com pour aster.com
Mais tu demandes l'IP de aster.com dans ton nslookup.
Il n'y en a pas de défini dans la zone...
Essaye de définir (par exemple) :
@ IN A 10.10.10.10
également : utilises plutôt la commande DIG pour tes interrogation, nslookup est obsolete.
26 nov. 2008 à 11:40
voilà ce que j'ai comme résultat
[root@localhost named]# /etc/init.d/named restart
Arrêt de named :
Démarrage de named : [ OK ]
[root@localhost named]# nslookup
> aster.com
Server: 212.217.0.1
Address: 212.217.0.1#53
Non-authoritative answer:
Name: aster.com
Address: 66.11.237.12
>
et pourtant mon fichier /etc/resolv.conf contient ceci:
; generated by /sbin/dhclient-script
search aster.com
nameserver 10.10.10.10
nameserver 212.217.0.1
~
~
~
et avec la commande set type=any j'ai ceci :
> set type=any
> aster.com
Server: 212.217.0.1
Address: 212.217.0.1#53
Non-authoritative answer:
aster.com nameserver = ns2.everydns.net.
aster.com nameserver = ns3.everydns.net.
aster.com nameserver = ns1.everydns.net.
aster.com nameserver = ns4.everydns.net.
Authoritative answers can be found from:
aster.com nameserver = ns4.everydns.net.
aster.com nameserver = ns1.everydns.net.
aster.com nameserver = ns2.everydns.net.
aster.com nameserver = ns3.everydns.net.
>