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 38 #subnet 10.254.239.0 netmask 255.255.255.224 { 39 # range 10.254.239.10 10.254.239.20; 40 # option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org; 41 #} 42 43 # This declaration allows BOOTP clients to get dynamic addresses, 44 # which we don't really recommend. 45 46 #subnet 10.254.239.32 netmask 255.255.255.224 { 47 # range dynamic-bootp 10.254.239.40 10.254.239.60; 48 # option broadcast-address 10.254.239.31; 49 # option routers rtr-239-32-1.example.org; 50 #} 51 52 # A slightly different configuration for an internal subnet. 53 subnet 192.168.1.0 netmask 255.255.255.0 { 54 range 192.168.1.5 192.168.1.100; 55 option domain-name-servers servidor.interno.org; 56 option domain-name "interno.org"; 57 option routers 192.168.1.1; 58 option broadcast-address 192.168.1.255; 59 default-lease-time 600; 60 max-lease-time 7200; 61 #} 62 63 # Hosts which require special configuration options can be listed in 64 # host statements. If no address is specified, the address will be 65 # allocated dynamically (if possible), but the host-specific information 66 # will still come from the host declaration. 67 68 #host passacaglia { 69 # hardware ethernet 0:0:c0:5d:bd:95; 70 # filename "vmunix.passacaglia"; 71 # server-name "toccata.fugue.com"; 72 #} 73 74 # Fixed IP addresses can also be specified for hosts. These addresses 75 # should not also be listed as being available for dynamic assignment. 76 # Hosts for which fixed IP addresses have been specified can boot using 77 # BOOTP or DHCP. Hosts for which no fixed address is specified can only 78 # be booted with DHCP, unless there is an address range on the subnet 79 # to which a BOOTP client is connected which has the dynamic-bootp flag 80 # set. 81 #host fantasia { 82 # hardware ethernet 08:00:07:26:c0:a5; 83 # fixed-address fantasia.fugue.com; 84 #} 85 86 # You can declare a class of clients and then do address allocation 87 # based on that. The example below shows a case where all clients 88 # in a certain class get addresses on the 10.17.224/24 subnet, and all 89 # other clients get addresses on the 10.0.29/24 subnet. 90 91 #class "foo" { 92 # match if substring (option vendor-class-identifier, 0, 4) = "SUNW"; 93 #} 94 95 #shared-network 224-29 { 96 # subnet 10.17.224.0 netmask 255.255.255.0 { 97 # option routers rtr-224.example.org; 98 # } 99 # subnet 10.0.29.0 netmask 255.255.255.0 { 100 # option routers rtr-29.example.org; 101 # } 102 # pool { 103 # allow members of "foo"; 104 # range 10.17.224.10 10.17.224.250; 105 # } 106 # pool { 107 # deny members of "foo"; 108 # range 10.0.29.10 10.0.29.230; 109 # } 110 #}