I am in the process of using OpenSSL to generate a device certificate for my 5508 WLC.
However, I had a question about DNS. The controller is on a guest network and is used for outside companies. I don't control their laptops/devices, and the controller is handing out a public DNS (184.108.40.206) for them to use. They simply log in and connect to the Internet.
I assume this is going to create a problem with the device certificate. Won't clients get a warning if they cannot resolve the name of the controller against the certificate? Aside from installing my own DNS server into that network, is there any way around this?
What I have done is create a certificate using your public domain and then adding an alias DNS record on your external DNS or public DNS server. Tie it to one of your public IP address and then use that public IP address for your VIP. That is a work around I have used.
Please rate helpful post and Cisco Support Community will donate to Kiva
It’s been a long road for our AireOS wireless controllers. In fact these products have been around Cisco in some form since 2005. As you may have heard, Cisco made the decision to End-of-Sale (EOS) these products last month.
That means that these AireOS ...
Hello Community, I have an issue where APs do not connect to the WLC. Connection is made over VPN. Until yesterday all 3 APfailed with below errors. We change the LAN connection to a cisco router and now one of the AP magically connected to the...
Where to download
Attached files on this post
Alternatively, cloud version (only summaries)
New implementation for the WLC Config Analyzer. it is a new re-write of the application, with clean up and improved checks
Support for IOS...
Cisco Champion Radio · S8|E6: Fastlane+ Optimizes Network and Device Communication
Cisco Fastlane+ is a co-developed solution with Apple that significantly improves the experience of any Wi-Fi 6 capable iPhone or iPad connected to a Cisco Catalyst 9130 A...
We are pleased to announce the immediate availability of the IOS-XE release 17.4.1 for the Catalyst Wireless Controllers. The new code is now posted on the CCO and can be found at this link: