Hey Andre - Good thought, and yes, I tried that as well. First tried pinging the server, then CISCO-CAPWAP with no suffix, then with suffix. I can ping the server, but that's it… The crazy thing is, I've been using this for several months in my lab and I've used the DNS server many times for this exact purpose. Hence, the reason I'm scratching my head…
sw2#ping 10.10.210.6 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.10.210.6, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/6 ms sw2#ping CISCO-CAPWAP-CONTROLLER Translating "CISCO-CAPWAP-CONTROLLER"...domain server (10.10.210.6) % Unrecognized host or address, or protocol not running. sw2#ping CISCO-CAPWAP-CONTROLLER.proctorlabs.com Translating "CISCO-CAPWAP-CONTROLLER.proctorlabs.com"...domain server (10.10.210.6) % Unrecognized host or address, or protocol not running. From: Andre Aubet <[email protected]<mailto:[email protected]>> Date: Friday, January 31, 2014 3:40 PM To: Jay Killion <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [OSL | CCIE_Wireless] DNS Troubleshooting Hi Jay, Did you try a ping to CISCO-CAPWAP... from the switch connecting the AP, and then from a device in the same subnet? Be sure to have configured dns-server and domain name on the devices before you can do your test. — Sent from Mailbox<https://www.dropbox.com/mailbox> for iPhone On Fri, Jan 31, 2014 at 10:33 PM, Jay Killion (jakillio) <[email protected]<mailto:[email protected]>> wrote: Hi all - I have very little experience with DNS, so when I have an issue I'm not really sure what to troubleshoot (after L1 – 3). For example, I'm currently trying to have an AP find a controller via DNS but having issues. 1 – I verify L1 – 3. The AP is getting an IP and can ping the DNS server, and vice versa. 2 – Console to the AP and see it is trying to resolve the correct name to the correct IP Translating "CISCO-CAPWAP-CONTROLLER.proctorlabs.com"...domain server (10.10.210.6) 3 – Double check my DNS forward lookup zone. It is "proctorlabs.com", with an "A" record of "CISCO-CAPWAP-CONTROLLER" translating to 10.10.112.10. 4 – I verify DNS service is running on the server. 5 – Restart the DNS service. Still no luck. 6 – Delete the zone and recreate. 7 – Reboot the Win2K3 server. Still not working. 8 – Look for anything wonky in the preconfigured switch, like an ACL on one of the SVI's blocking DNS. Nothing… At this point I can't think of anything else to even troubleshoot. In the actual lab, I would likely just resort to option 43 to get the AP's connect and simply know I was throwing away points. What else would you look at that I may have missed? Thanks Jay Killion, CCIE #17873
_______________________________________________ Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos :: iPexpert on YouTube: www.youtube.com/ipexpertinc
