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
