nouveau fichier : sisr1/tp01-02/srv-dhcp/dhcpd.conf

nouveau fichier : sisr1/tp01-02/srv-dhcp/nat.sh
	nouveau fichier : sisr1/tp01-02/srv-dns1/db.sio1lab.lan
	nouveau fichier : sisr1/tp01-02/srv-dns1/db.sio1lab.lan.rev
	nouveau fichier : sisr1/tp01-02/srv-dns1/hosts
	nouveau fichier : sisr1/tp01-02/srv-dns1/interfaces
	nouveau fichier : sisr1/tp01-02/srv-dns1/named.conf.local
	nouveau fichier : sisr1/tp01-02/srv-dns1/named.conf.options
	nouveau fichier : sisr1/tp01-02/srv-dns1/resolv.conf
	nouveau fichier : sisr1/tp01-02/srv-dns2/db.sio1lab.lan
	nouveau fichier : sisr1/tp01-02/srv-dns2/db.sio1lab.lan.rev
	nouveau fichier : sisr1/tp01-02/srv-dns2/hosts
	nouveau fichier : sisr1/tp01-02/srv-dns2/interfaces
	nouveau fichier : sisr1/tp01-02/srv-dns2/named.conf.local
	nouveau fichier : sisr1/tp01-02/srv-dns2/named.conf.options
	nouveau fichier : sisr1/tp01-02/srv-dns2/resolv.conf

	nouveau fichier : sisr1/tp01-02/srv-dhcp/dhcpd.conf
	nouveau fichier : sisr1/tp01-02/srv-dhcp/nat.sh
	nouveau fichier : sisr1/tp01-02/srv-dns1/db.sio1lab.lan
	nouveau fichier : sisr1/tp01-02/srv-dns1/db.sio1lab.lan.rev
	nouveau fichier : sisr1/tp01-02/srv-dns1/hosts
	nouveau fichier : sisr1/tp01-02/srv-dns1/interfaces
	nouveau fichier : sisr1/tp01-02/srv-dns1/named.conf.local
	nouveau fichier : sisr1/tp01-02/srv-dns1/named.conf.options
	nouveau fichier : sisr1/tp01-02/srv-dns1/resolv.conf
	nouveau fichier : sisr1/tp01-02/srv-dns2/db.sio1lab.lan
	nouveau fichier : sisr1/tp01-02/srv-dns2/db.sio1lab.lan.rev
	nouveau fichier : sisr1/tp01-02/srv-dns2/hosts
	nouveau fichier : sisr1/tp01-02/srv-dns2/interfaces
	nouveau fichier : sisr1/tp01-02/srv-dns2/named.conf.local
	nouveau fichier : sisr1/tp01-02/srv-dns2/named.conf.options
	nouveau fichier : sisr1/tp01-02/srv-dns2/resolv.conf
This commit is contained in:
Guillaume Emorine 2024-01-30 15:09:56 +01:00
parent 2a2a273c3f
commit a8eb4897c4
16 changed files with 362 additions and 0 deletions

116
sisr1/tp01-02/srv-dhcp/dhcpd.conf Executable file
View File

@ -0,0 +1,116 @@
# 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 604800;
max-lease-time 604800;
option domain-name-servers 192.168.0.121;
option domain-name-servers 192.168.0.122;
# 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 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.5 192.168.2.99;
option routers 192.168.0.120;
}
host xp-master {
hardware ethernet 08:00:27:77:70:0D;
fixed-address 192.168.2.167;
}
# 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 fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.example.com;
#}
# 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;
# }
#}

6
sisr1/tp01-02/srv-dhcp/nat.sh Executable file
View File

@ -0,0 +1,6 @@
#!/bin/bash
sudo sysctl net.ipv4.ip_forward="1"
nft add table basic_nat_table
nft add chain basic_nat_table prerouting {type nat hook prerouting priority 0 \; }
nft add chain basic_nat_table postrouting {type nat hook postrouting priority 0 \; }
nft add rule basic_nat_table postrouting masquerade

View File

@ -0,0 +1,33 @@
;
; BIND data file for local loopback interface
;
$TTL 604800
@ IN SOA deb-dns1-ge.sio1lab.lan. root.sio1lab.lan. (
2635478965 ; Serial
21600 ; Refresh
3600 ; Retry
2419200 ; Expire
86400 ) ; Negative Cache TTL
IN NS deb-dns1-ge.sio1lab.lan.
IN NS deb-dns2-ge.sio1lab.lan.
IN A 192.168.0.120
IN A 192.168.0.121
IN A 192.168.0.140
IN A 192.168.0.141
IN A 192.168.0.142
deb-dhcp-ge IN A 192.168.0.120
deb-dns1-ge IN A 192.168.0.121
deb-dns2-ge IN A 192.168.0.122
deb-dhcp-jp IN A 192.168.0.141
deb-dns-jp IN A 192.168.0.140
deb-dns2-jp IN A 192.168.0.142
dhcp IN CNAME deb-dhcp-ge
dns1 IN CNAME deb-dns1-ge
dns2 IN CNAME deb-dns2-ge
dhcpjp IN CNAME deb-dhcp-jp
dns1jp IN CNAME deb-dns-jp
dns2jp IN CNAME deb-dns2-jp

View File

@ -0,0 +1,28 @@
;
; BIND data file for local loopback interface
;
$TTL 604800
@ IN SOA deb-dns1-ge.sio1lab.lan. root.sio1lab.lan. (
2635478965 ; Serial
21600 ; Refresh
3600 ; Retry
2419200 ; Expire
86400 ) ; Negative Cache TTL
IN NS deb-dns1-ge.sio1lab.lan.
IN NS deb-dns2-ge.sio1lab.lan.
deb-dhcp-ge IN A 192.168.0.120
deb-dns1-ge IN A 192.168.0.121
deb-dns2-ge IN A 192.168.0.122
deb-dhcp-jp IN A 192.168.0.141
deb-dns-jp IN A 192.168.0.140
deb-dns2-jp IN A 192.168.0.142
120 IN PTR deb-dhcp-ge.sio1lab.lan.
121 IN PTR deb-dns1-ge.sio1lab.lan.
122 IN PTR deb-dns2-ge.sio1lab.lan.
140 IN PTR deb-dns-jp.sio1lab.lan.
141 IN PTR deb-dhcp-jp.sio1lab.lan.
142 IN PTR deb-dns2-jp.sio1lab.lan.

7
sisr1/tp01-02/srv-dns1/hosts Executable file
View File

@ -0,0 +1,7 @@
127.0.0.1 localhost
127.0.1.1 dns1-ge.sio.lan dns1-ge
192.168.0.24 bookworm-jp.sio.lan bookworm-jp
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

View File

@ -0,0 +1,14 @@
# 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
allow-hotplug enp0s3
iface enp0s3 inet static
address 192.168.0.121/24
gateway 192.168.0.1

View File

@ -0,0 +1,21 @@
//
// Do any local configuration here
//
// zone directe
zone "sio1lab.lan" {
type master;
file "/etc/bind/db.sio1lab.lan";
};
// zone inverse
zone "0.168.192.in-addr.arpa" {
type master;
notify no;
file "/etc/bind/db.sio1lab.lan.rev";
};
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

View File

@ -0,0 +1,25 @@
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;
10.121.38.8;
};
//========================================================================
// 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 no;
listen-on-v6 { any; };
};

View File

@ -0,0 +1,2 @@
search sio1lab.lan
nameserver 127.0.0.1

View File

@ -0,0 +1,20 @@
$ORIGIN .
$TTL 604800 ; 1 week
sio1lab.lan IN SOA deb-dns1-ge.sio1lab.lan. root.sio1lab.lan. (
2635478965 ; serial
21600 ; refresh (6 hours)
3600 ; retry (1 hour)
2419200 ; expire (4 weeks)
86400 ; minimum (1 day)
)
NS deb-dns1-ge.sio1lab.lan.
NS deb-dns2-ge.sio1lab.lan.
A 192.168.0.120
A 192.168.0.121
$ORIGIN sio1lab.lan.
deb-dhcp-ge A 192.168.0.120
deb-dns1-ge A 192.168.0.121
deb-dns2-ge A 192.168.0.122
dhcp CNAME deb-dhcp-ge
dns1 CNAME deb-dns1-ge
dns2 CNAME deb-dns2-ge

View File

@ -0,0 +1,18 @@
$ORIGIN .
$TTL 604800 ; 1 week
0.168.192.in-addr.arpa IN SOA deb-dns1-ge.sio1lab.lan. root.sio1lab.lan. (
2635478965 ; serial
21600 ; refresh (6 hours)
3600 ; retry (1 hour)
2419200 ; expire (4 weeks)
86400 ; minimum (1 day)
)
NS deb-dns1-ge.sio1lab.lan.
NS deb-dns2-ge.sio1lab.lan.
$ORIGIN 0.168.192.in-addr.arpa.
120 PTR deb-dhcp-ge.sio1lab.lan.
121 PTR deb-dns1-ge.sio1lab.lan.
122 PTR deb-dns2-ge.sio1lab.lan.
deb-dhcp-ge A 192.168.0.120
deb-dns1-ge A 192.168.0.121
deb-dns2-ge A 192.168.0.122

7
sisr1/tp01-02/srv-dns2/hosts Executable file
View File

@ -0,0 +1,7 @@
127.0.0.1 localhost
127.0.1.1 dns2-ge.sio.lan dns2-ge
192.168.0.24 bookworm-jp.sio.lan bookworm-jp
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

View File

@ -0,0 +1,14 @@
# 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
allow-hotplug enp0s3
iface enp0s3 inet static
address 192.168.0.122/24
gateway 192.168.0.1

View File

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

View File

@ -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 {
// 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; };
};

View File

@ -0,0 +1,2 @@
search sio1lab.lan
server 127.0.0.1