diff --git a/sisr1/tp03_reseaux_prive/serveur_service/db.monlabo.lan b/sisr1/tp03_reseaux_prive/serveur_service/db.monlabo.lan
new file mode 100644
index 0000000..b42ad73
--- /dev/null
+++ b/sisr1/tp03_reseaux_prive/serveur_service/db.monlabo.lan
@@ -0,0 +1,24 @@
+;
+; BIND data file for local loopback interface
+;
+$TTL	604800
+@	IN	SOA	srv-service.monlabo.lan. root.srv-service.monlabo.lan.(
+			   2		; Serial
+			 604800		; Refresh
+			  86400		; Retry
+			2419200		; Expire
+			 604800 )	; Negative Cache TTL
+	NS srv-service.monlabo.lan.
+srv-service	IN A	172.16.0.1
+srv-admin-sv	IN A	172.16.0.254
+
+srvdns		CNAME	srv-service.monlabo.lan.
+srvdns1		CNAME	srv-service.monlabo.lan.
+dns		CNAME	srv-service.monlabo.lan.
+dns1		CNAME	srv-service.monlabo.lan.
+srvdhcp		CNAME	srv-service.monlabo.lan.
+dhcp		CNAME	srv-service.monlabo.lan.
+srvadmin	CNAME	srv-admin-sv.monlabo.lan
+router		CNAME	srv-admin-sv.monlabo.lan
+gateway		CNAME	srv-admin-sv.monlabo.lan
+
diff --git a/sisr1/tp03_reseaux_prive/serveur_service/db.monlabo.lan.rev b/sisr1/tp03_reseaux_prive/serveur_service/db.monlabo.lan.rev
new file mode 100644
index 0000000..581399d
--- /dev/null
+++ b/sisr1/tp03_reseaux_prive/serveur_service/db.monlabo.lan.rev
@@ -0,0 +1,16 @@
+;
+; BIND data file for local loopback interface
+;
+$TTL	604800
+@	IN	SOA	srv-service.monlabo.lan. root.srv-service.monlabo.lan.(
+			   2		; Serial
+			 604800		; Refresh
+			  86400		; Retry
+			2419200		; Expire
+			 604800 )	; Negative Cache TTL
+	NS srv-service.monlabo.lan.
+srv-service	IN A	172.16.0.1
+
+1	PTR	srv-service.monlabo.lan.
+254	PTR	srv-admin-sv.monlabo.lan.
+
diff --git a/sisr1/tp03_reseaux_prive/serveur_service/dhcpd.conf b/sisr1/tp03_reseaux_prive/serveur_service/dhcpd.conf
new file mode 100644
index 0000000..a74f9f8
--- /dev/null
+++ b/sisr1/tp03_reseaux_prive/serveur_service/dhcpd.conf
@@ -0,0 +1,120 @@
+# dhcpd.conf
+#
+# Sample configuration file for ISC dhcpd
+#
+
+# option definitions common to all supported networks...
+# option domain-name "example.org";
+# option domain-name-servers ns1.example.org, ns2.example.org;
+
+default-lease-time 600;
+max-lease-time 7200;
+
+subnet 172.16.0.0 netmask 255.255.255.0 {
+   option subnet-mask 255.255.255.0;		# masque de sous-réseau
+   option broadcast-address 172.16.0.255;	# adresse de broadcast 
+   range 172.16.0.10 172.16.0.110;		# plage d'adresse
+   option routers 172.16.0.254;			# passerelle
+   option domain-name-servers 172.16.0.1;	# ip srv dns
+   option domain-name "monlabo.lan";		# nom domaine
+}
+
+host srv-dns2{
+   hardware ethernet 08:00:27:1b:f3:2f;
+   fixed-address 172.16.0.2;
+} 
+# The ddns-updates-style parameter controls whether or not the server will
+# attempt to do a DNS update when a lease is confirmed. We default to the
+# behavior of the version 2 packages ('none', since DHCP v2 didn't
+# have support for DDNS.)
+ddns-update-style none;
+
+# If this DHCP server is the official DHCP server for the local
+# network, the authoritative directive should be uncommented.
+#authoritative;
+
+# Use this to send dhcp log messages to a different log file (you also
+# have to hack syslog.conf to complete the redirection).
+#log-facility local7;
+
+# No service will be given on this subnet, but declaring it helps the 
+# DHCP server to understand the network topology.
+
+#subnet 10.152.187.0 netmask 255.255.255.0 {
+#}
+
+# This is a very basic subnet declaration.
+
+#subnet 10.254.239.0 netmask 255.255.255.224 {
+#  range 10.254.239.10 10.254.239.20;
+#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
+#}
+
+# This declaration allows BOOTP clients to get dynamic addresses,
+# which we don't really recommend.
+
+#subnet 10.254.239.32 netmask 255.255.255.224 {
+#  range dynamic-bootp 10.254.239.40 10.254.239.60;
+#  option broadcast-address 10.254.239.31;
+#  option routers rtr-239-32-1.example.org;
+#}
+
+# A slightly different configuration for an internal subnet.
+#subnet 10.5.5.0 netmask 255.255.255.224 {
+#  range 10.5.5.26 10.5.5.30;
+#  option domain-name-servers ns1.internal.example.org;
+#  option domain-name "internal.example.org";
+#  option routers 10.5.5.1;
+#  option broadcast-address 10.5.5.31;
+#  default-lease-time 600;
+#  max-lease-time 7200;
+#}
+
+# Hosts which require special configuration options can be listed in
+# host statements.   If no address is specified, the address will be
+# allocated dynamically (if possible), but the host-specific information
+# will still come from the host declaration.
+
+#host passacaglia {
+#  hardware ethernet 0:0:c0:5d:bd:95;
+#  filename "vmunix.passacaglia";
+#  server-name "toccata.example.com";
+#}
+
+# Fixed IP addresses can also be specified for hosts.   These addresses
+# should not also be listed as being available for dynamic assignment.
+# Hosts for which fixed IP addresses have been specified can boot using
+# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
+# be booted with DHCP, unless there is an address range on the subnet
+# to which a BOOTP client is connected which has the dynamic-bootp flag
+# set.
+host srv-admin {
+  hardware ethernet 08:00:27:cd:ea:0f;
+  fixed-address 172.16.0.254;
+}
+
+# You can declare a class of clients and then do address allocation
+# based on that.   The example below shows a case where all clients
+# in a certain class get addresses on the 10.17.224/24 subnet, and all
+# other clients get addresses on the 10.0.29/24 subnet.
+
+#class "foo" {
+#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
+#}
+
+#shared-network 224-29 {
+#  subnet 10.17.224.0 netmask 255.255.255.0 {
+#    option routers rtr-224.example.org;
+#  }
+#  subnet 10.0.29.0 netmask 255.255.255.0 {
+#    option routers rtr-29.example.org;
+#  }
+#  pool {
+#    allow members of "foo";
+#    range 10.17.224.10 10.17.224.250;
+#  }
+#  pool {
+#    deny members of "foo";
+#    range 10.0.29.10 10.0.29.230;
+#  }
+#}
diff --git a/sisr1/tp03_reseaux_prive/serveur_service/interfaces b/sisr1/tp03_reseaux_prive/serveur_service/interfaces
new file mode 100644
index 0000000..ae060e3
--- /dev/null
+++ b/sisr1/tp03_reseaux_prive/serveur_service/interfaces
@@ -0,0 +1,15 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+source /etc/network/interfaces.d/*
+
+# The loopback network interface
+auto lo
+iface lo inet loopback
+
+# The primary network interface
+# This is an autoconfigured IPv6 interface
+auto enp0s3
+iface enp0s3 inet static
+	address 172.16.0.1/24
+	gateway 172.16.0.254
diff --git a/sisr1/tp03_reseaux_prive/serveur_service/named.conf.local b/sisr1/tp03_reseaux_prive/serveur_service/named.conf.local
new file mode 100644
index 0000000..448a6ed
--- /dev/null
+++ b/sisr1/tp03_reseaux_prive/serveur_service/named.conf.local
@@ -0,0 +1,20 @@
+//
+// Do any local configuration here
+//
+
+// Consider adding the 1918 zones here, if they are not used in your
+// organization
+//include "/etc/bind/zones.rfc1918";
+
+// zone directe
+        zone "monlabo.lan" {
+             type master;
+             file "/etc/bind/db.monlabo.lan";
+        };
+
+// zone inverse 
+	zone "0.16.172.in-addr.arpa" {
+	     type master;
+             notify no;
+             file "/etc/bind/db.monlabo.lan.rev";
+	};
diff --git a/sisr1/tp03_reseaux_prive/serveur_service/named.conf.options b/sisr1/tp03_reseaux_prive/serveur_service/named.conf.options
new file mode 100644
index 0000000..963892f
--- /dev/null
+++ b/sisr1/tp03_reseaux_prive/serveur_service/named.conf.options
@@ -0,0 +1,24 @@
+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 {
+		10.121.38.7;
+	 };
+
+	//========================================================================
+	// 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; };
+};