TRES URGENT!!!
- Voila la réponse de la machine:
[code]root@mondher-VirtualBox:/var/lib/named/etc/bind# nslookup ns.n2tr.com
Server: 192.168.1.64
Address: 192.168.1.64#53
Name: ns.n2tr.com
Address: 192.168.1.64
root@mondher-VirtualBox:/var/lib/named/etc/bind# nslookup 192.168.1.64
Server: 192.168.1.64
Address: 192.168.1.64#53
64.1.168.192.in-addr.arpa name = ns.n2tr.com.[/code]
l’adresse du serveur comme vous voyer 192.168.1.64 sur un reseau local
les fichiers de configuration sont:
#named.conf:
[code]include “/etc/bind/named.conf.options”;
include “/etc/bind/named.conf.local”;
include “/etc/bind/named.conf.default-zones”;
include “/etc/bind/kerberos-n2tr-com_rndc-key”;
acl internals { 127.0.0.0/8; 192.168.1.0/24; };
include “/etc/bind/ns-miniprojet-com_rndc-key”;
controls {
inet 127.0.0.1 port 953 allow { 127.0.0.1; };
};
// 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”;
};
include “/etc/bind/named.conf.local”;[/code]
#named.conf.local
[code]include “/etc/bind/named.conf.log”;
zone “miniprojet.com” {
type master;
file “/var/cache/bind/db.miniprojet.com”;
forwarders {};
allow-update { key ns-miniprojet-com_rndc-key; };
};
zone “1.168.192.in-addr.arpa” {
type master;
file “/var/cache/bind/db.miniprojet.com.inv”;
forwarders {};
allow-update { key ns-miniprojet-com_rndc-key; };
};
// Consider adding the 1918 zones here, if they are not used in your
// organization
include “/etc/bind/zones.rfc1918”;[/code]
#named.conf.options:
[code]options {
directory “/var/cache/bind”;
query-source address * port *;
forward only;
forwarders { 192.168.1.1; };
listen-on-v6 { none; };
listen-on { 127.0.0.1; 192.168.1.64; };
allow-transfer { none; };
auth-nxdomain no; # conform to RFC1035
allow-query { internals; };
allow-recursion { internals; };
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk. See http://www.kb.cert.org/vuls/id/800113
// 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 {
// 0.0.0.0;
// };
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
version none;
};[/code]
#le fichier /etc/hosts:
127.0.0.1 localhost miniprojet.com
127.0.1.1 mondher-VirtualBox
#le fichier /etc/resolv.conf:
Generated by NetworkManager
nameserver 192.168.1.64
nameserver 172.20.1.3
nameserver 172.20.1.5
#le fichier db.miniprojet.com:
[code]$TTL 3600
@ IN SOA sid.miniprojet.com. root.miniprojet.com. (
2007010401 ; Serial
3600 ; Refresh [1h]
600 ; Retry [10m]
86400 ; Expire [1d]
600 ) ; Negative Cache TTL [1h]
;
@ IN NS sid.miniprojet.com.
@ IN MX 10 sid.miniprojet.com.
sid IN A 192.168.1.64
etch IN A 192.168.1.2
pop IN CNAME sid
www IN CNAME sid
mail IN CNAME sid[/code]
#le fichier db.miniprojet.com.inv
[code]@ IN SOA sid.miniprojet.com. root.miniprojet.com. (
2007010401 ; Serial
3600 ; Refresh [1h]
600 ; Retry [10m]
86400 ; Expire [1d]
600 ) ; Negative Cache TTL [1h]
;
@ IN NS sid.miniprojet.com.
1 IN PTR sid.miniprojet.com.
2 IN PTR etch.miniprojet.com.[/code]
maintenant la question qui se pose: comme vous voyer je n’ai pas configurerr le domaine ns.n2tr.com mais ns.miniprojet.com, j’ai rien compris d’ou vient la réponse du domaine ns.n2tr.com tandis-que le domaine ns.miniprojet.com ne répond pas? s’ils vous plait me répondre en urgence, la remise des miniprojet et trés proche, et merci pour votre collaboration
).
