Howdy folks,
We are moving from a legacy LDAP domain into a fun new Active Directory forest with all these new domains. Funny thing is, the Microsoft DHCP service has no provisions for searching multiple DNS suffixes, which they recommend as a best practice. Loving this!
Anyway, I thought that I would look into Cisco's DHCP service. Looks like there is a provision on attribute 119. Here's a snip from RFC3397:
*************************************************
- Example
Below is an example encoding of a search list consisting of "eng.apple.com." and "marketing.apple.com.":
+---+---+---+---+---+---+---+---+---+---+---+ |119| 9 | 3 |'e'|'n'|'g'| 5 |'a'|'p'|'p'|'l'| +---+---+---+---+---+---+---+---+---+---+---+
+---+---+---+---+---+---+---+---+---+---+---+ |119| 9 |'e'| 3 |'c'|'o'|'m'| 0 | 9 |'m'|'a'| +---+---+---+---+---+---+---+---+---+---+---+
+---+---+---+---+---+---+---+---+---+---+---+ |119| 9 |'r'|'k'|'e'|'t'|'i'|'n'|'g'|xC0|x04| +---+---+---+---+---+---+---+---+---+---+---+
Note:
i. The encoding has been split (for this example) into three Domain Search Options. All Domain Search Options are logically concatenated into one block of data before being interpreted by the client.
ii. The encoding of "eng.apple.com." ends with a zero, the null root label, to mark the end of the name, as required by RFC 1035.
*************************************************
So, my question is: How would I add this to my DHCP scope? I create the pool and see there is an "options" function from which I can choose option 119. Has anyone got this to work correctly?