<?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: Zone director cached old system name in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4335#M532</link>
    <description>Hello Donald, can you look at this KB article and see if this is the solution you need.
&lt;BR /&gt;
&lt;A href="https://support.ruckuswireless.com/answers/000001837" rel="nofollow"&gt;https://support.ruckuswireless.com/an...&lt;/A&gt;
&lt;BR /&gt;
thanks,
&lt;BR /&gt;
Reese</description>
    <pubDate>Wed, 08 Jan 2014 16:15:26 GMT</pubDate>
    <dc:creator>reese_williams_</dc:creator>
    <dc:date>2014-01-08T16:15:26Z</dc:date>
    <item>
      <title>Zone director cached old system name</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4331#M528</link>
      <description>I have Zone Director 1100 I have change the system name of ZD to reflect the new DNS name of ZD. Now my clients can not access the web authentication page, it gets redirected to the old system name of the ZD.</description>
      <pubDate>Wed, 08 Jan 2014 14:58:24 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4331#M528</guid>
      <dc:creator>donald_scott_60</dc:creator>
      <dc:date>2014-01-08T14:58:24Z</dc:date>
    </item>
    <item>
      <title>Re: Zone director cached old system name</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4332#M529</link>
      <description>Clear the DNS cache of the clients.</description>
      <pubDate>Wed, 08 Jan 2014 15:42:45 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4332#M529</guid>
      <dc:creator>rob_coote</dc:creator>
      <dc:date>2014-01-08T15:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: Zone director cached old system name</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4333#M530</link>
      <description>Hello Rob, 
&lt;BR /&gt;&lt;BR /&gt;
Thank you for your reply. DNS cache has been cleared from client's laptop.
&lt;BR /&gt;
I get the same problem when tested on a new laptop.</description>
      <pubDate>Wed, 08 Jan 2014 15:56:12 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4333#M530</guid>
      <dc:creator>donald_scott_60</dc:creator>
      <dc:date>2014-01-08T15:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: Zone director cached old system name</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4334#M531</link>
      <description>A couple of other things to check:
&lt;BR /&gt;&lt;BR /&gt;
NSLookup from those clients and see what IP the hostname resolves to. Ensure that is the same hostname in the redirect setting on the controller.
&lt;BR /&gt;&lt;BR /&gt;
Check for a A record on your DNS server that might still point to the incorrect hostname/IP.</description>
      <pubDate>Wed, 08 Jan 2014 16:04:31 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4334#M531</guid>
      <dc:creator>rob_coote</dc:creator>
      <dc:date>2014-01-08T16:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: Zone director cached old system name</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4335#M532</link>
      <description>Hello Donald, can you look at this KB article and see if this is the solution you need.
&lt;BR /&gt;
&lt;A href="https://support.ruckuswireless.com/answers/000001837" rel="nofollow"&gt;https://support.ruckuswireless.com/an...&lt;/A&gt;
&lt;BR /&gt;
thanks,
&lt;BR /&gt;
Reese</description>
      <pubDate>Wed, 08 Jan 2014 16:15:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4335#M532</guid>
      <dc:creator>reese_williams_</dc:creator>
      <dc:date>2014-01-08T16:15:26Z</dc:date>
    </item>
    <item>
      <title>Re: Zone director cached old system name</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4336#M533</link>
      <description>Hello Reese,
&lt;BR /&gt;&lt;BR /&gt;
Thank you very much for your help. Re-importing the certificate has fixed the problem &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Thu, 09 Jan 2014 15:55:06 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4336#M533</guid>
      <dc:creator>donald_scott_60</dc:creator>
      <dc:date>2014-01-09T15:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Zone director cached old system name</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4337#M534</link>
      <description>Still an issue on 10.1.2.0.120.&amp;nbsp;</description>
      <pubDate>Thu, 14 Mar 2019 15:13:47 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Zone-director-cached-old-system-name/m-p/4337#M534</guid>
      <dc:creator>nickzourdos</dc:creator>
      <dc:date>2019-03-14T15:13:47Z</dc:date>
    </item>
  </channel>
</rss>

