<?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 DNS Flag Day and Check Point in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/DNS-Flag-Day-and-Check-Point/m-p/27523#M5571</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may have heard about DNS flag day (&lt;A class="link-titled" href="https://dnsflagday.net/" title="https://dnsflagday.net/"&gt;2019 | DNS flag day&lt;/A&gt;&amp;nbsp;) and are now asking yourself how will this impact your environment.&amp;nbsp; &amp;nbsp;A number of DNS providers "&lt;SPAN style="color: #373737; background-color: #ffffff;"&gt;have agreed to coordinate removing accommodations for non-compliant DNS implementations from their software or services, on or around&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;STRONG style="color: #373737; background-color: #ffffff; border: 0px; font-weight: bold; font-size: 16px;"&gt;February 1st 2019&lt;/STRONG&gt;&lt;SPAN style="color: #373737; background-color: #ffffff;"&gt;. This change will affect only sites operating non-compliant software."&amp;nbsp; This primarily impacts authoritative DNS servers.&amp;nbsp; As a result of these changes, you may see&amp;nbsp;&lt;/SPAN&gt;your Check Point gateway running IPS drop certain traffic due to Non Compliant DNS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gateways running R77.30 JHF 345 and above (including R80.10 and R80.20) are not impacted.&amp;nbsp; If you're running a lower version and cannot upgrade then you will need to set the IPS protection "Non Compliant DNS" to detect.&amp;nbsp; &amp;nbsp;For further information, please see&amp;nbsp;sk112578 or reach out to your local SE.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 Jan 2019 21:33:28 GMT</pubDate>
    <dc:creator>Samuel_Shiflett</dc:creator>
    <dc:date>2019-01-25T21:33:28Z</dc:date>
    <item>
      <title>DNS Flag Day and Check Point</title>
      <link>https://community.checkpoint.com/t5/General-Topics/DNS-Flag-Day-and-Check-Point/m-p/27523#M5571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may have heard about DNS flag day (&lt;A class="link-titled" href="https://dnsflagday.net/" title="https://dnsflagday.net/"&gt;2019 | DNS flag day&lt;/A&gt;&amp;nbsp;) and are now asking yourself how will this impact your environment.&amp;nbsp; &amp;nbsp;A number of DNS providers "&lt;SPAN style="color: #373737; background-color: #ffffff;"&gt;have agreed to coordinate removing accommodations for non-compliant DNS implementations from their software or services, on or around&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;STRONG style="color: #373737; background-color: #ffffff; border: 0px; font-weight: bold; font-size: 16px;"&gt;February 1st 2019&lt;/STRONG&gt;&lt;SPAN style="color: #373737; background-color: #ffffff;"&gt;. This change will affect only sites operating non-compliant software."&amp;nbsp; This primarily impacts authoritative DNS servers.&amp;nbsp; As a result of these changes, you may see&amp;nbsp;&lt;/SPAN&gt;your Check Point gateway running IPS drop certain traffic due to Non Compliant DNS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gateways running R77.30 JHF 345 and above (including R80.10 and R80.20) are not impacted.&amp;nbsp; If you're running a lower version and cannot upgrade then you will need to set the IPS protection "Non Compliant DNS" to detect.&amp;nbsp; &amp;nbsp;For further information, please see&amp;nbsp;sk112578 or reach out to your local SE.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jan 2019 21:33:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/DNS-Flag-Day-and-Check-Point/m-p/27523#M5571</guid>
      <dc:creator>Samuel_Shiflett</dc:creator>
      <dc:date>2019-01-25T21:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Flag Day and Check Point</title>
      <link>https://community.checkpoint.com/t5/General-Topics/DNS-Flag-Day-and-Check-Point/m-p/27524#M5572</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just checked one of my R77.30 gateways and 345 isnt listed when I checked for updates .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UPDATE: You must search the "Add Hotfxes from the Could" using:&amp;nbsp;&lt;SPAN style="font-size: 12.0pt;"&gt;Check_Point_R77_30_JUMBO_HF_1_Bundle_T345_FULL.tgz&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Jan 2019 18:02:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/DNS-Flag-Day-and-Check-Point/m-p/27524#M5572</guid>
      <dc:creator>Nick_Keith</dc:creator>
      <dc:date>2019-01-28T18:02:34Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Flag Day and Check Point</title>
      <link>https://community.checkpoint.com/t5/General-Topics/DNS-Flag-Day-and-Check-Point/m-p/27525#M5573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's because JHF 345 is an "ongoing" hotfix, which means it won't be listed in CPUSE unless you get the identifier from TAC.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Only "recommended" jumbo hotfixes&amp;nbsp;are listed in CPUSE.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Jan 2019 01:00:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/DNS-Flag-Day-and-Check-Point/m-p/27525#M5573</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-01-29T01:00:51Z</dc:date>
    </item>
  </channel>
</rss>

