Hi
We have our environment configured with a DNS recorded configured for aruba-master pointing to our Controller.
If the AP-303 is connected to the same subnet as the controller, it does come up as a CAP.
However if the AP-303 is connected to a different subnet (that has a route to the controller) the AP doesn’t attempt to the connect to the controller, nor does it look up aruba-master from the DNS server.
The AP boots, and looks up pool.ntp.org and devices.arubanetworks.com; then tries to connect to both.
Cheers