If you want to do a ping test, I would suggest just pinging "cisco-capwap-controller" without adding in the domain suffix. That way, you validate that the AP has learned the domain suffix appropriately in addition to DNS functionality and later 3 connectivity. The AP will automatically add in the domain suffix that it learned via DHCP or static config.
My guess in your case, there was a fat finger or something off with the DNS suffix config in the DHCP pool. The ping is probably the ultimate test as it gives you the most information. But as you are looking at the AP logs, when you see the entry that it's trying to resolve cisco-capwap-controller, you can get helpful info there. First, you see if a DNS suffix is being appended to the host name and what it is. Next you see the IP address of the DNS server (unicast IP or a 255.255.255.255 broadcast). If the DNS resolution works, it will also say [OK] at the end of the line. If you don't get the [OK], either DNS isn't working, or there is no entry for the host name. If you do get the [OK], DNS resolved to something. But to find out what it resolves to, you should just do the ping test. The ping test gives you all of this info, plus the IP that the host name resolved to and if you have layer 3 connectivity. Hope that helps. Regards, Jeff Rensink : Sr Instructor : iPexpert <http://www.ipexpert.com/> CCIE # 24834 :: Wireless / R&S :: World-Class Cisco Certification Training Direct: +1.810.326.1444 :: Free Videos <http://www.youtube.com/ipexpertinc> :: Free Training / Product Offerings <http://www.facebook.com/ipexpert> :: CCIE Blog <http://blog.ipexpert.com/> :: Twitter <http://www.twitter.com/ipexpert> On Tue, Jan 7, 2014 at 10:15 AM, Jay Killion (jakillio) <[email protected]>wrote: > 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]> > Date: Tuesday, January 7, 2014 9:43 AM > To: "[email protected]" <[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 >
_______________________________________________ Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos :: iPexpert on YouTube: www.youtube.com/ipexpertinc
