From 802428a5f9f3677f643df2287c9f5c32bff0e1cd Mon Sep 17 00:00:00 2001 From: "anthony.boillot" Date: Mon, 3 Feb 2025 10:56:19 +0100 Subject: [PATCH 1/3] dns1 --- sisr1/tp02-dns/dns1/db.sio-ab.lan.rev | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 sisr1/tp02-dns/dns1/db.sio-ab.lan.rev diff --git a/sisr1/tp02-dns/dns1/db.sio-ab.lan.rev b/sisr1/tp02-dns/dns1/db.sio-ab.lan.rev new file mode 100644 index 0000000..1867090 --- /dev/null +++ b/sisr1/tp02-dns/dns1/db.sio-ab.lan.rev @@ -0,0 +1,16 @@ +; +; BIND data file for local loopback interface +; +$TTL 604800 +@ IN SOA dns1-ab.sio-ab.lan. root ( + 2 ; Serial + 604800 ; Refresh + 86400 ; Retry + 2419200 ; Expire + 604800 ) ; Negative Cache TTL +; + IN NS dns1-ab.sio.lan. + IN NS dns2-ab.sio.lan. +160 IN PTR deb-dhcp-ab.sio-ab.lan. +161 IN PTR dns1-ab.sio-ab.lan. +162 IN PTR dns2-ab.sio-ab.lan. From 116065a9bd4565e79d6600f07e3538dbba62c747 Mon Sep 17 00:00:00 2001 From: "anthony.boillot" Date: Mon, 3 Feb 2025 10:58:08 +0100 Subject: [PATCH 2/3] dns1 fini --- sisr1/tp02-dns/dns1/db.sio-ab.lan | 20 ++++++++++++++++++++ sisr1/tp02-dns/dns1/named.conf.local | 20 ++++++++++++++++++++ sisr1/tp02-dns/dns1/resolv.conf | 4 ++++ 3 files changed, 44 insertions(+) create mode 100644 sisr1/tp02-dns/dns1/db.sio-ab.lan create mode 100644 sisr1/tp02-dns/dns1/named.conf.local create mode 100644 sisr1/tp02-dns/dns1/resolv.conf diff --git a/sisr1/tp02-dns/dns1/db.sio-ab.lan b/sisr1/tp02-dns/dns1/db.sio-ab.lan new file mode 100644 index 0000000..5bdc758 --- /dev/null +++ b/sisr1/tp02-dns/dns1/db.sio-ab.lan @@ -0,0 +1,20 @@ +; +; BIND data file for local loopback interface +; +$TTL 604800 +@ IN SOA dns1-ab.sio-ab.lan. root.dns1-ab.sio-ab.lan. ( + 2 ; Serial + 604800 ; Refresh + 86400 ; Retry + 2419200 ; Expire + 604800 ) ; Negative Cache TTL + NS dns1-ab.sio-ab.lan. + NS dns2-ab.sio-ab.lan. + A 192.168.0.162 +dns1-ab.sio-ab.lan. A 192.168.0.161 +; +@ IN NS localhost. +@ IN A 127.0.0.1 +@ IN A 192.168.0.160 +@ IN AAAA ::1 +; diff --git a/sisr1/tp02-dns/dns1/named.conf.local b/sisr1/tp02-dns/dns1/named.conf.local new file mode 100644 index 0000000..6701173 --- /dev/null +++ b/sisr1/tp02-dns/dns1/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 "sio-ab.lan" { + type master; + file "/etc/bind/db.sio-ab.lan"; + }; + + // zone inverse + zone "0.168.192.in-addr.arpa" { + type master; + notify no; + file "/etc/bind/db.sio-ab.lan.rev"; + }; diff --git a/sisr1/tp02-dns/dns1/resolv.conf b/sisr1/tp02-dns/dns1/resolv.conf new file mode 100644 index 0000000..1c60899 --- /dev/null +++ b/sisr1/tp02-dns/dns1/resolv.conf @@ -0,0 +1,4 @@ +domain sio-ab.lan +search sio-ab.lan +nameserver 192.168.0.161 +nameserver 10.121.38.7 From bb20f9842cc6213aa2e9bd39c38b8709640f9617 Mon Sep 17 00:00:00 2001 From: "anthony.boillot" Date: Mon, 3 Feb 2025 11:01:58 +0100 Subject: [PATCH 3/3] dhcp fini --- sisr1/tp02-dns/dhcp/dhcpd.conf | 111 +++++++++++++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 sisr1/tp02-dns/dhcp/dhcpd.conf diff --git a/sisr1/tp02-dns/dhcp/dhcpd.conf b/sisr1/tp02-dns/dhcp/dhcpd.conf new file mode 100644 index 0000000..f843d30 --- /dev/null +++ b/sisr1/tp02-dns/dhcp/dhcpd.conf @@ -0,0 +1,111 @@ +# 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 3600; +max-lease-time 604800; + +# 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 192.168.2.0 netmask 255.255.255.0 { + range 192.168.2.10 192.168.2.100; + option routers 192.168.2.1; + option domain-name-servers 10.121.38.7; + option domain-name-servers 192.168.0.161; + option domain-name "dns1-ab.sio-ab.lan"; +} + # 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 wxp1 { + hardware ethernet 08:00:27:77:70:0D; + fixed-address 192.168.2.50; +} + +# 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; +# } +#}