Hello. We have two main sites, one in California and one in New York. We have a DHCP server in each location that generally serves each geographic location. We use traditional scopes to hand out addresses to each locations networks and everything was working fine. Someone then added a superscope at each site contains scopes within it for the other corresponding site. I am guessing this was done for redundancy. After this was done, computers randomly go over the WAN and get their DHCP addresses from the other site. From my reading, it shouldn't do this unless the local DHCP server is down. This is causing problems as we don't necessarily always have our DHCP reservations setup in the corresponding superscope across the wan. Our servers haven't experienced any issues in terms of network outages or errors etc so the local DHCP server has been available during these occurrences.
Example: A DHCP client in California had an address of 10.1.10.100. It was shut down for work over night. When we booted it up, even though it has a reservation in the California scope of 10.1.10.x, it went across the wan to New York and pulled an address of 10.1.10.124 from the New York superscope of 10.1.10.124 (the California backup superscope).
Does anyone have any ideas why we might be experience this behavior? My thoughts are that in this scenario, the usage of superscopes is not even necessary and we should be using regular DHCP scopes, but I also need to find out why we are seeing
this behavior.