Well, I ended up just deleted the DHCP scope and creating it again – which fixed the issue. Not sure why as I triple checked the domain and DNS server in the old scope, which is a bit frustrating.
From: Jay Killion <[email protected]<mailto:[email protected]>> Date: Tuesday, January 7, 2014 9:43 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: AP WLC Discovery - DNS Hi all - I'm having an issue getting my AP to discover the controller via DNS. It pulls an IP, the correct domain, and then tries to resolve CISCO-CAPWAP-CONTROLLER.Proctorlabs.com. It's trying to resolve at the correct IP (10.10.210.6), but just sits there till you get the "could not discover WLC using DHCP…" and the process starts over. But here's the part that has me stumped… From that AP, even while I'm waiting for it to try and resolve, I can successfully ping CISCO-CAPWAP-CONTROLLER.Proctorlabs.com. Every single time, the AP resolves the name via DNS, gets the correct IP (10.10.112.20), and sends 5 successful pings. So, I know I'm good L1 – 7 from AP to DNS server. I've tried rebooting both the server and AP for sanity, but still no luck. Any suggestions? Jay Killion, CCIE #17873 R/S
_______________________________________________ Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos :: iPexpert on YouTube: www.youtube.com/ipexpertinc
