DHCP Scope Policies and FQDN

Question

Does something special have to be enabled to use FQDN to assign an IP range?

I have successfully used Vendor Class Identifiers and MAC addresses to hand out specific IP ranges (192.168.30.x for access points, 192.168.40.0 for VMs, etc...). However I don't seem to have that option for FQDN. With a FQDN policy I can set unique options like 003 Router and such, but "IP Address Range" is greyed out.

Here's the scenario (with made up data). We have lets say 75 iPads that connect wirelessly. 25 belong to the training department, 25 belong to HR, and 25 belong to employment. Our naming convention sets them up as Training-1, Training-2 and so on and respectively HR-1, HR-2 for all the devices.

They're all going to be the same vendor class and MAC address ranges, so can we use the unique naming convention to specify ranges of IPs? Imagine this:

iPad Names	IP Range
Training-*	192.168.60.1-50
Employment-*	192.168.60.51-100
HR-*	192.168.60.101-150

Before I get the question, "Why would you want to do that?" These iPads all connect on the same SSID and associated VLAN, but we want to apply unique ACLs to each "group" of devices. Training has access to Server-1, HR can get to Server-1 & Server-3, Employment can get to Server-2... The layer-3 ACLs can only be defined by IPs and we don't want to have to set static addresses to every device to comply with the appropriate range.

I'd take a solution or a suggestion for a different approach.

Answer 1

Hello,

A policy with conditions based on fully qualified domain name can have configuration settings for DNS but not for options or IP address ranges.

Please reference the picture below for further understanding:

What's New in DHCP | Microsoft Learn

Instead of assigning IP addresses directly based on FQDN, you can segregate your network into VLANs based on your naming convention. For example, you can put all "Training-" devices in one VLAN and "Employment-" devices in another. Then, assign IP address ranges to these VLANs in your router's settings.

Regards,

Karlie

Answer 2

ROFL!

How could I have missed that? OK, bummer. I didn't really want to have multiple SSIDs and multiple SVIs on the Layer-3 for these tablets.