What DNS entry to use for WLC with firmware version 6.0 or later so an Access Point can determine the controller’s IP address?

What DNS entry to use for WLC with firmware version 6.0 or later so an Access Point can determine the controller’s IP address?
A. DNS A record with controller’s hostname
B. DHCP option 43
C. cisco-capwap-controller
D. cisco-lwapp-controller

cisco-exams

2 thoughts on “What DNS entry to use for WLC with firmware version 6.0 or later so an Access Point can determine the controller’s IP address?

  1. A DHCP option is not a DNS record. The answer should be C

    The following layer 3 CAPWAP discovery options are supported:
    1. Broadcast on the local subnet
    2. Local NVRAM list of the previously joined controller, previous mobility group members, and administrator primed controller through the console port
    3. Over the Air Provisioning (OTAP) (subsequently removed in version 6.0.170.0 code)
    4. DHCP Option 43 returned from the DHCP server
    5. DNS lookup for “CISCO-CAPWAP-CONTROLLER.localdomain”

  2. In Layer 2 mode, they were required to be on the same subnet. In Layer 3 mode, the controller and LAP are essentially playing hide and seek in the network. If you do not tell the LAP where the controller is via DHCP option 43, DNS resolution of “Cisco-lwapp-controller@local_domain”, or statically configure it, the LAP does not know where in the network to find the management interface of the controller.

    In addition to these methods, the LAP does automatically look on the local subnet for controllers with a 255.255.255.255 local broadcast. Also, the LAP remembers the management IP address of any controller it joins across reboots. Therefore, if you put the LAP first on the local subnet of the management interface, it will find the controller’s management interface and remember the address. This is called priming. This does not help find the controller if you replace a LAP later on. Therefore, Cisco recommends using the DHCP option 43 or DNS methods.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.