<?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: Strange DNS Problems in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524932#M309622</link>
    <description>&lt;P&gt;Is The Client IP assignment  NAT mode or Bridge mode?&lt;/P&gt;</description>
    <pubDate>Wed, 30 Mar 2022 11:26:30 GMT</pubDate>
    <dc:creator>aleabrahao</dc:creator>
    <dc:date>2022-03-30T11:26:30Z</dc:date>
    <item>
      <title>Strange DNS Problems</title>
      <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524931#M309621</link>
      <description>&lt;P&gt;I have a DNS problem in a network of 500 users, some devices connect to the wifi in one of the ssid and after connection ok they use chrome that tells them the dns did not respond i check the logs in meraki and see "DNS server did not respond".&lt;/P&gt;&lt;P&gt;I'm using google 8.8.8.8 and 8.8.4.4 but for some reason it gives me this errors but I can use a computer and ping 8.8.8.8 and 8.8.4.4 no problem but can't get dns in chrome our other web browser.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Mar 2022 10:55:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524931#M309621</guid>
      <dc:creator>NunoFlora</dc:creator>
      <dc:date>2022-03-30T10:55:51Z</dc:date>
    </item>
    <item>
      <title>Re: Strange DNS Problems</title>
      <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524932#M309622</link>
      <description>&lt;P&gt;Is The Client IP assignment  NAT mode or Bridge mode?&lt;/P&gt;</description>
      <pubDate>Wed, 30 Mar 2022 11:26:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524932#M309622</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2022-03-30T11:26:30Z</dc:date>
    </item>
    <item>
      <title>Re: Strange DNS Problems</title>
      <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524933#M309623</link>
      <description>&lt;P&gt;&lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/73835"&gt;@NunoFlora&lt;/A&gt; : Check this thread &lt;/P&gt;&lt;P&gt;&lt;A href="https://community.meraki.com/t5/Wireless-LAN/Weird-DNS-Issues/m-p/5352#M970" target="_blank"&gt;https://community.meraki.com/t5/Wireless-LAN/Weird-DNS-Issues/m-p/5352#M970&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Mar 2022 12:14:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524933#M309623</guid>
      <dc:creator>inderdeepsingh1</dc:creator>
      <dc:date>2022-03-30T12:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: Strange DNS Problems</title>
      <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524934#M309624</link>
      <description>&lt;P&gt;If you use nslookup, can you resolve a DNS name?&lt;/P&gt;&lt;P&gt;Chrome changed over to using DNS over HTTPS at some stage, so it may not be sending DNS queries as you think.  I think it was optional initially and then became the default.  You could try a test and disable DNS over HTTPS on one machine and see if that changes the problem.&lt;/P&gt;&lt;P&gt;&lt;A href="https://pureinfotech.com/enable-dns-over-https-chrome/" target="_self" rel="nofollow noopener noreferrer"&gt;https://pureinfotech.com/enable-dns-over-https-chrome/&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Are you using any third-party filtering software, either for DNS or HTTPS?&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2022 19:08:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524934#M309624</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2022-03-31T19:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: Strange DNS Problems</title>
      <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524935#M309625</link>
      <description>&lt;P&gt;I would also mention DNS over TLS as a possible problem. Try to do a trace route anc check for rules that block traffic to the DNS Server/s.&lt;/P&gt;&lt;P&gt;Another thing that might be required at some point is DNSSEC, give 9.9.9.9 a chance. (Cloudflare is of course a good one, too, but not in terms of security and threat defending)&lt;/P&gt;</description>
      <pubDate>Sat, 02 Apr 2022 15:30:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524935#M309625</guid>
      <dc:creator>MerryAki</dc:creator>
      <dc:date>2022-04-02T15:30:20Z</dc:date>
    </item>
    <item>
      <title>Re: Strange DNS Problems</title>
      <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524936#M309626</link>
      <description>&lt;P&gt;&lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/71894"&gt;@MerryAki&lt;/A&gt; I have to agree with you here.&lt;/P&gt;&lt;P&gt;My thoughts:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;If he can ping successfully, but can’t visit web pages through browsers; then we know the issue lies with “host names not resolving”. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;I would capture the DNS traffic and find out where it’s getting dropped. Then check the ACL to see if DNS traffic is allowed on port 53. Cheers!&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 03 Apr 2022 08:21:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524936#M309626</guid>
      <dc:creator>securingnimbu5</dc:creator>
      <dc:date>2022-04-03T08:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: Strange DNS Problems</title>
      <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524937#M309627</link>
      <description>&lt;P&gt;I still don't know what the problem is but changed dns to 1.1.1.1 and solved all the dns problems&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2022 15:31:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524937#M309627</guid>
      <dc:creator>NunoFlora</dc:creator>
      <dc:date>2022-04-12T15:31:55Z</dc:date>
    </item>
    <item>
      <title>Re: Strange DNS Problems</title>
      <link>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524938#M309628</link>
      <description>&lt;P&gt;Or try preselecting Google or Cisco Umbrella DNS&lt;/P&gt;&lt;P&gt;But yes, cloudflare is performing better &lt;SPAN class="lia-unicode-emoji" title=":victory_hand:"&gt;&lt;span class="lia-unicode-emoji" title=":victory_hand:"&gt;✌️&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2022 15:37:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/strange-dns-problems/m-p/5524938#M309628</guid>
      <dc:creator>MerryAki</dc:creator>
      <dc:date>2022-04-12T15:37:57Z</dc:date>
    </item>
  </channel>
</rss>

