Wireless Access

Occasional Contributor I

Controller discovery via DHCP or DNS

I have controllers in California and New York that are configured in a master local topology and the AP

s are able to locate the master via a DNS lookup. I'm now building a master controller for EMEA where I use the same DNS domain so I want to provide controller info via DHCP instead of DNS.


I've configured options 43 and 60 with their appropriate values but the AP's are still registering to the master in California. How can I force the EMEA AP's to register to the controller provided by DHCP and ignore the DNS name?

Occasional Contributor I

Re: Controller discovery via DHCP or DNS

I've now changed the domain suffix so aruba-master is no longer resolvable so the AP's won't reach the California controller but they still aren't showing up on the in-region master. I've set up the following in DHCP


Option 43 = <IP of the controller VLAN interface>

Option 60 = ArubaAP


Is there anything else needed beyond the normal network, mask, and gateway?

Guru Elite

Re: Controller discovery via DHCP or DNS

What type of dhcp server are you using?  Here are the instructions for Microsoft's DHCP server.

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Video Knowledge Base
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Search Airheads
Showing results for 
Search instead for 
Did you mean: