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