Superscope DHCP leases and configuration set up

dhcpdhcp-serverdomain-name-systemnetworking

Hello I wanted to see if someone could help with a network problem I am having. Right now we have a super-scope and scopes of 192.168.50.1 and 192.168.51.1, as of now both are activated but only 192.168.50.1 is handing our leases, 192.168.51 wont. here is a summary of our network

Gateway: watchguard firebox x750e for our router/gateway at 192.168.50.1 I set up as a secondary IP address 192.168.51.1

Server: Server 2008 r2 standard, running our DNS @ 192.168.50.242 and 8.8.8.8 as a secondary, AD, and DHCP. On that NIC card i have 192.168.50.242 as the IP address and 192.168.51.242 as a secondary. 192.168.50.1 as the default gateway and 192.168.51.1 as a secondary.

Im am not very knowledgeable at this but as far as i have researched after adding a super scope and activating scopes, they should automatically start handing out addresses and I cant figure out why only one does. any help at all would be appreciated.

Best Answer

There is probably no reason to keep it like this, it's unnecessarily complicated. 192.168.50.0/24 and 192.168.51.0/24 can be combined into one subnet, 192.168.50.0/23, so you could reconfigure that on the DHCP server and get rid of the Superscope. Then configure it as 192.168.50.0/23 on the router/vlan as well. The only issue is going to be subnet mask and gateway on statically configured devices, so you might have numerous touch points. DHCP clients will pick up the new subnet mask next time they renew.

It's probably the case that you ran out of IPs on 192.168.50.0/24 at some point and another was added as a "secondary" as a quick and dirty way to get more address space on that wire/vlan. Superscope is a way to join those two /24's on the DHCP side telling the DHCP server that both of these scopes are on the same wire and thus recognize that any clients or relay agents coming from either subnet should be treated as being on the same wire/vlan. This is more commonly used when the subnets are non-continguous, e.g., if it was 192.168.50.0/24 originally then you added 192.168.66.0/24 as a secondary network to get more space.

The behavior you see is thus normal. You won't see the DHCP server start handing out addresses from the newly-enabled scope (under the Superscope) until all addresses in the first scope (192.168.50.1) are all used up. And existing DHCP clients will continue to directly renew the IP they already have.