Ticket #63536: dhcpd.conf

File dhcpd.conf, 4.3 KB (added by Kyosho (Frank Fallon), 3 years ago)

DHCP Configuration File

Line 
1# dhcpd.conf
2#
3# Live configuration file for ISC dhcpd - DHCP Server that updates BIND9 DNS Server dynamically
4#
5# option definitions common to all supported networks...
6option domain-name "zmmapple.com";
7option domain-name-servers 172.16.10.21, 192.168.2.219, 8.8.8.8;
8option domain-search "zmmapple.com", "dc.mro.local", "mro.local";
9
10default-lease-time 100800;
11max-lease-time 115200;
12
13# The ddns-updates-style parameter controls whether or not the server will
14# attempt to do a DNS update when a lease is confirmed.
15# Options: ad-hoc, interim, standard, none
16# Conflict detection off allow WiFi/Ethernet switching on client to override hostname.
17ddns-updates on;
18ddns-update-style standard;
19update-static-leases on;
20ddns-domainname "zmmapple.com";
21update-conflict-detection off;
22
23include "/opt/local/etc/rndc.key";
24
25zone zmmapple.com. {
26        primary 127.0.0.1;
27        key rndc-key;
28}
29
30zone 10.16.172.in-addr.arpa. {
31        primary 127.0.0.1;
32        key rndc-key;
33}
34
35# If this DHCP server is the official DHCP server for the local
36# network, the authoritative directive should be uncommented.
37authoritative;
38
39############################################
40# SUBNET: 172.16.10.0/24
41subnet 172.16.10.0 netmask 255.255.255.0 {
42        range                   172.16.10.200 172.16.10.239;
43        option subnet-mask      255.255.255.0;
44        option routers          172.16.10.31;
45}
46############################################
47
48# SUBNET: 192.168.12.0/24
49#subnet 192.168.12.0 netmask 255.255.255.0 {
50#       range                   192.168.12.200 192.168.12.239;
51#       option subnet-mask      255.255.255.0;
52#       option routers          192.168.12.1;
53#}
54############################################
55
56# Use this to send dhcp log messages to a different log file (you also
57# have to hack syslog.conf to complete the redirection).
58#log-facility local7;
59
60# No service will be given on this subnet, but declaring it helps the
61# DHCP server to understand the network topology.
62
63#subnet 10.152.187.0 netmask 255.255.255.0 {
64#}
65
66# This is a very basic subnet declaration.
67
68#subnet 10.254.239.0 netmask 255.255.255.224 {
69#  range 10.254.239.10 10.254.239.20;
70#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
71#}
72
73# This declaration allows BOOTP clients to get dynamic addresses,
74# which we don't really recommend.
75
76#subnet 10.254.239.32 netmask 255.255.255.224 {
77#  range dynamic-bootp 10.254.239.40 10.254.239.60;
78#  option broadcast-address 10.254.239.31;
79#  option routers rtr-239-32-1.example.org;
80#}
81
82# A slightly different configuration for an internal subnet.
83#subnet 10.5.5.0 netmask 255.255.255.224 {
84#  range 10.5.5.26 10.5.5.30;
85#  option domain-name-servers ns1.internal.example.org;
86#  option domain-name "internal.example.org";
87#  option subnet-mask 255.255.255.224;
88#  option routers 10.5.5.1;
89#  option broadcast-address 10.5.5.31;
90#  default-lease-time 600;
91#  max-lease-time 7200;
92#}
93
94# Hosts which require special configuration options can be listed in
95# host statements.   If no address is specified, the address will be
96# allocated dynamically (if possible), but the host-specific information
97# will still come from the host declaration.
98
99#host passacaglia {
100#  hardware ethernet 0:0:c0:5d:bd:95;
101#  filename "vmunix.passacaglia";
102#  server-name "toccata.example.com";
103#}
104
105# Fixed IP addresses can also be specified for hosts.   These addresses
106# should not also be listed as being available for dynamic assignment.
107# Hosts for which fixed IP addresses have been specified can boot using
108# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
109# be booted with DHCP, unless there is an address range on the subnet
110# to which a BOOTP client is connected which has the dynamic-bootp flag
111# set.
112#host fantasia {
113#  hardware ethernet 08:00:07:26:c0:a5;
114#  fixed-address fantasia.example.com;
115#}
116
117# You can declare a class of clients and then do address allocation
118# based on that.   The example below shows a case where all clients
119# in a certain class get addresses on the 10.17.224/24 subnet, and all
120# other clients get addresses on the 10.0.29/24 subnet.
121
122#class "foo" {
123#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
124#}
125
126#shared-network 224-29 {
127#  subnet 10.17.224.0 netmask 255.255.255.0 {
128#    option routers rtr-224.example.org;
129#  }
130#  subnet 10.0.29.0 netmask 255.255.255.0 {
131#    option routers rtr-29.example.org;
132#  }
133#  pool {
134#    allow members of "foo";
135#    range 10.17.224.10 10.17.224.250;
136#  }
137#  pool {
138#    deny members of "foo";
139#    range 10.0.29.10 10.0.29.230;
140#  }
141#}