Keita NISHIMOTO | 3b8b9c0 | 2018-10-09 09:40:01 +0900 | [diff] [blame] | 1 | # |
| 2 | # Sample configuration file for ISC dhcpd for Debian |
| 3 | # |
| 4 | # Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as |
| 5 | # configuration file instead of this file. |
| 6 | # |
| 7 | # |
| 8 | |
| 9 | # The ddns-updates-style parameter controls whether or not the server will |
| 10 | # attempt to do a DNS update when a lease is confirmed. We default to the |
| 11 | # behavior of the version 2 packages ('none', since DHCP v2 didn't |
| 12 | # have support for DDNS.) |
| 13 | ddns-update-style none; |
| 14 | |
| 15 | # option definitions common to all supported networks... |
| 16 | option domain-name "example.org"; |
| 17 | option domain-name-servers ns1.example.org, ns2.example.org; |
| 18 | |
| 19 | default-lease-time 600; |
| 20 | max-lease-time 7200; |
| 21 | |
| 22 | # If this DHCP server is the official DHCP server for the local |
| 23 | # network, the authoritative directive should be uncommented. |
| 24 | #authoritative; |
| 25 | |
| 26 | # Use this to send dhcp log messages to a different log file (you also |
| 27 | # have to hack syslog.conf to complete the redirection). |
| 28 | log-facility local7; |
| 29 | |
| 30 | # No service will be given on this subnet, but declaring it helps the |
| 31 | # DHCP server to understand the network topology. |
| 32 | |
| 33 | #subnet 10.152.187.0 netmask 255.255.255.0 { |
| 34 | #} |
| 35 | |
| 36 | # This is a very basic subnet declaration. |
| 37 | subnet 182.21.0.0 netmask 255.255.0.0 { |
Keita NISHIMOTO | ca4da5f | 2018-10-15 22:48:52 +0900 | [diff] [blame^] | 38 | range 182.21.0.1 182.21.0.128; |
Keita NISHIMOTO | 3b8b9c0 | 2018-10-09 09:40:01 +0900 | [diff] [blame] | 39 | option routers 182.21.0.254; |
| 40 | } |
| 41 | |
Keita NISHIMOTO | 3b8b9c0 | 2018-10-09 09:40:01 +0900 | [diff] [blame] | 42 | #subnet 10.254.239.0 netmask 255.255.255.224 { |
| 43 | # range 10.254.239.10 10.254.239.20; |
| 44 | # option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org; |
| 45 | #} |
| 46 | |
| 47 | # This declaration allows BOOTP clients to get dynamic addresses, |
| 48 | # which we don't really recommend. |
| 49 | |
| 50 | #subnet 10.254.239.32 netmask 255.255.255.224 { |
| 51 | # range dynamic-bootp 10.254.239.40 10.254.239.60; |
| 52 | # option broadcast-address 10.254.239.31; |
| 53 | # option routers rtr-239-32-1.example.org; |
| 54 | #} |
| 55 | |
| 56 | # A slightly different configuration for an internal subnet. |
| 57 | #subnet 10.5.5.0 netmask 255.255.255.224 { |
| 58 | # range 10.5.5.26 10.5.5.30; |
| 59 | # option domain-name-servers ns1.internal.example.org; |
| 60 | # option domain-name "internal.example.org"; |
| 61 | # option subnet-mask 255.255.255.224; |
| 62 | # option routers 10.5.5.1; |
| 63 | # option broadcast-address 10.5.5.31; |
| 64 | # default-lease-time 600; |
| 65 | # max-lease-time 7200; |
| 66 | #} |
| 67 | |
| 68 | # Hosts which require special configuration options can be listed in |
| 69 | # host statements. If no address is specified, the address will be |
| 70 | # allocated dynamically (if possible), but the host-specific information |
| 71 | # will still come from the host declaration. |
| 72 | |
| 73 | #host passacaglia { |
| 74 | # hardware ethernet 0:0:c0:5d:bd:95; |
| 75 | # filename "vmunix.passacaglia"; |
| 76 | # server-name "toccata.fugue.com"; |
| 77 | #} |
| 78 | |
| 79 | # Fixed IP addresses can also be specified for hosts. These addresses |
| 80 | # should not also be listed as being available for dynamic assignment. |
| 81 | # Hosts for which fixed IP addresses have been specified can boot using |
| 82 | # BOOTP or DHCP. Hosts for which no fixed address is specified can only |
| 83 | # be booted with DHCP, unless there is an address range on the subnet |
| 84 | # to which a BOOTP client is connected which has the dynamic-bootp flag |
| 85 | # set. |
| 86 | #host fantasia { |
| 87 | # hardware ethernet 08:00:07:26:c0:a5; |
| 88 | # fixed-address fantasia.fugue.com; |
| 89 | #} |
| 90 | |
| 91 | # You can declare a class of clients and then do address allocation |
| 92 | # based on that. The example below shows a case where all clients |
| 93 | # in a certain class get addresses on the 10.17.224/24 subnet, and all |
| 94 | # other clients get addresses on the 10.0.29/24 subnet. |
| 95 | |
| 96 | #class "foo" { |
| 97 | # match if substring (option vendor-class-identifier, 0, 4) = "SUNW"; |
| 98 | #} |
| 99 | |
| 100 | #shared-network 224-29 { |
| 101 | # subnet 10.17.224.0 netmask 255.255.255.0 { |
| 102 | # option routers rtr-224.example.org; |
| 103 | # } |
| 104 | # subnet 10.0.29.0 netmask 255.255.255.0 { |
| 105 | # option routers rtr-29.example.org; |
| 106 | # } |
| 107 | # pool { |
| 108 | # allow members of "foo"; |
| 109 | # range 10.17.224.10 10.17.224.250; |
| 110 | # } |
| 111 | # pool { |
| 112 | # deny members of "foo"; |
| 113 | # range 10.0.29.10 10.0.29.230; |
| 114 | # } |
| 115 | #} |