First, I'd always use the official private network ranges for testing. For Class A addresses, use 10.0.0.0/8.
However it's unlikely you'd want to maintain a network this size. I typically use either private Class C addresses like 192.168.1.0/24, which supports 253 addresses, or private Class Bs like 172.168.0.0/16 which support 65,534.
Using 10.0.0.0/8 and 255.0.0.0 means you're allocating addresses to 2^24 hosts/networks, or nearly 17 million addresses. Hardly anyone outside of large providers manage networks of that size.
You need to start by assigning the server a "static" address in the range you're using on the interface that faces the local private network. A common numbering scheme with a Class-C range is to assign the outbound router, or "default gateway," an address like 192.168.1.1, and all of the other hosts with addresses between 192.168.1.2 and 192.168.1.254. Often the DHCP server is located on the router.
On class-C networks the "network address," 192.168.1.0, and the "broadcast address," 192.168.1.255, are reserved and cannot be assigned by DHCP. Similar rules apply to class-B and class-C networks.
With a class-C numbering scheme you might use
Code:
group aquila-legion {
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.51 192.168.1.200;
option domain-name-servers 8.8.8.8;
option routers 192.168.1.1;
default-lease-time 3600;
max-lease-time 86400;
}
}
This gives DHCP clients addresses in the range 192.168.1.51-200, and tells the clients to send all outbound traffic to the default gateway, 192.168.1.1. Usually that's a router configured to send traffic upstream, typically to the public Internet.
