<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: WLC discovery using DNS in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552938#M50236</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've setup the DNS name and let it use my local domain, which it does if you don't specify it. It has worked fine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just add the A record of cisco-lwapp-controller with the Management IP Address of the controller. It has to be the management, not the AP manager interface. DNS domain should have no relevance. I haven't seen any reference to DNS domain on a WLC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've set this up for several clients and it works every time. Common mistake is using the AP Mgr interface address.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 May 2006 21:19:46 GMT</pubDate>
    <dc:creator>drees</dc:creator>
    <dc:date>2006-05-05T21:19:46Z</dc:date>
    <item>
      <title>WLC discovery using DNS</title>
      <link>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552937#M50235</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone successfully got AP's discovering the WLC using the DNS name CISCO-LWAPP-CONTROLLER?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I cant seem to get the dns server to work properly.  I added a host called CISCO-LWAPP-CONTROLLER but it keeps appending the domain name to the end of it.  I notice that the documentation states the discovery looks for CISCO-LWAPP-CONTROLLER@localdomain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using MS DNS server.  Can anyone help or provide a screenshot of the correct setup on dns.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 19:03:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552937#M50235</guid>
      <dc:creator>firestartest</dc:creator>
      <dc:date>2021-07-04T19:03:24Z</dc:date>
    </item>
    <item>
      <title>Re: WLC discovery using DNS</title>
      <link>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552938#M50236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've setup the DNS name and let it use my local domain, which it does if you don't specify it. It has worked fine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just add the A record of cisco-lwapp-controller with the Management IP Address of the controller. It has to be the management, not the AP manager interface. DNS domain should have no relevance. I haven't seen any reference to DNS domain on a WLC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've set this up for several clients and it works every time. Common mistake is using the AP Mgr interface address.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 May 2006 21:19:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552938#M50236</guid>
      <dc:creator>drees</dc:creator>
      <dc:date>2006-05-05T21:19:46Z</dc:date>
    </item>
    <item>
      <title>Re: WLC discovery using DNS</title>
      <link>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552939#M50237</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was curious about the same issue, and ran across this document:  &lt;A class="jive-link-custom" href="http://www.cos-cug.org/Presentations/Wireless.ppt" target="_blank"&gt;www.cos-cug.org/Presentations/Wireless.ppt&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems to suggest that you put the entry in as:&lt;/P&gt;&lt;P&gt;cisco-lwapp-controller.localdomain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have an Infoblox DNS appliance, and plan to try this, as well as your suggestion.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 May 2006 00:43:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552939#M50237</guid>
      <dc:creator>richard.martin</dc:creator>
      <dc:date>2006-05-06T00:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: WLC discovery using DNS</title>
      <link>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552940#M50238</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It was the .localdomain part causing me problems.  When I captured packets I noticed that the AP was querying DNS for CISCO-LWAPP-CONTROLLER and the DNS respone was "not found".  NSLOOKUP from a client gave the same response, but clients in the Active Directory domain resolved the address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I added the DHCP option DOMAIN NAME with the name of my AD domain.  The AP then queried for CISCO-LWAPP-CONTROLLER.test.co.uk and this worked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I summary I had&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DHCP scope for AP's.&lt;/P&gt;&lt;P&gt;DNS servers in options&lt;/P&gt;&lt;P&gt;Defailt Gateway in options&lt;/P&gt;&lt;P&gt;Domain Name in options&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 May 2006 09:04:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-discovery-using-dns/m-p/552940#M50238</guid>
      <dc:creator>firestartest</dc:creator>
      <dc:date>2006-05-08T09:04:50Z</dc:date>
    </item>
  </channel>
</rss>

