Supprision des fichiers named.conf du srv-dns2

sisr1/tp03-reseau-prive/srv-dns2/dns/named.conf.local

@@ -1,24 +0,0 @@
-//
-// Do any local configuration here
-//
-	// zone direct
-	zone "monlabo.lan" {
-		type slave;
-		file "/etc/bind/db.monlabo.lan";
-		masters {172.16.0.254;} ;
-		masterfile-format text;
-	};
-
-	// zone inverse
-	zone "0.16.172.in-addr.arpa" {
-		type slave;
-		notify no;
-		file "/etc/bind/db.monlabo.lan.rev";
-		masters { 172.16.0.254; } ;
-		masterfile-format text;
-	};
-
-// Consider adding the 1918 zones here, if they are not used in your
-// organization
-//include "/etc/bind/zones.rfc1918";
-

sisr1/tp03-reseau-prive/srv-dns2/dns/named.conf.options

@@ -1,24 +0,0 @@
-options {
-	directory "/var/cache/bind";
-
-	// 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;
-	// };
-
-	//========================================================================
-	// If BIND logs error messages about the root key being expired,
-	// you will need to update your keys.  See https://www.isc.org/bind-keys
-	//========================================================================
-	dnssec-validation auto;
-
-	listen-on-v6 { any; };
-};