<?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: DNS Controls in Unleashed</title>
    <link>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42370#M4152</link>
    <description>Thumb's Up!</description>
    <pubDate>Thu, 20 Dec 2018 20:50:44 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2018-12-20T20:50:44Z</dc:date>
    <item>
      <title>DNS Controls</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42367#M4149</link>
      <description>Hello,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Our WCF (Umbrella) relies on devices using specific DNS servers.&amp;nbsp;Currently I am able to statically assign a DNS server and bypass this security. Is there a way to prevent clients from connecting if they have statically assigned a DNS server?&lt;BR /&gt;&lt;BR /&gt;We are using R510 and R310 Unleashed.</description>
      <pubDate>Wed, 19 Dec 2018 15:28:18 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42367#M4149</guid>
      <dc:creator>matthew_smith_8</dc:creator>
      <dc:date>2018-12-19T15:28:18Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Controls</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42368#M4150</link>
      <description>We have a CLI WLAN configuration command "force-dhcp" which will disallow clients with a static IP, but I don't think we look at router-provided or client defined DNS hosts.</description>
      <pubDate>Wed, 19 Dec 2018 22:26:56 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42368#M4150</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-12-19T22:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Controls</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42369#M4151</link>
      <description>Easy solution, block out bound DNS requests on your firewall port 53 outbound, only allow your dc's outbound on port 53 which you should do anyways as part of a good Cyber Security&amp;nbsp;plan.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Thu, 20 Dec 2018 20:49:31 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42369#M4151</guid>
      <dc:creator>tim_brumbaugh</dc:creator>
      <dc:date>2018-12-20T20:49:31Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Controls</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42370#M4152</link>
      <description>Thumb's Up!</description>
      <pubDate>Thu, 20 Dec 2018 20:50:44 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42370#M4152</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-12-20T20:50:44Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Controls</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42371#M4153</link>
      <description>Thanks for the replies guys. Tim that's a great point. We have, currently, chosen not to deploy Firewalls though, since this is for our branch office public Guest networks and are entirely separated from our corporate network.</description>
      <pubDate>Fri, 21 Dec 2018 14:10:11 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42371#M4153</guid>
      <dc:creator>matthew_smith_8</dc:creator>
      <dc:date>2018-12-21T14:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Controls</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42372#M4154</link>
      <description>If this is for your guest internet traffic I am a little confused.&amp;nbsp; Does it matter if you guest traffic uses a different / Public dns server to get to the internet.&amp;nbsp; If they are totally separated&amp;nbsp;physically or via a vlan then I am not sure of the issue.&amp;nbsp; If it were me I always have control of any traffic wired or wireless within any of my infrastructure and always have firewalls in place even if it is just for guest traffic.&amp;nbsp; Client isolation is turned on and the quest traffic is on a DMZ.&amp;nbsp; I am a consultant and work with a lot of banks, schools and businesses and the amount of attacks has increased so much&amp;nbsp;in the past couple of years that it has become a defacto standard&amp;nbsp; to deploy firewalls at any business site that has access to the internet, if you are not doing this your are setting yourself up for failure.&amp;nbsp; The hackers have turned their attention to the small and medium sized business as they have become more lucrative and easier to hack either via lack of security standards, phishing or social engineering and we don't do any managed customers with out certain standards in place period.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Fri, 28 Dec 2018 17:16:37 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/DNS-Controls/m-p/42372#M4154</guid>
      <dc:creator>tim_brumbaugh</dc:creator>
      <dc:date>2018-12-28T17:16:37Z</dc:date>
    </item>
  </channel>
</rss>

