<?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 have a sinking feeling that wildcard fqdn's are not supported...? in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/have-a-sinking-feeling-that-wildcard-fqdn-s-are-not-supported/m-p/29719#M6072</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;looking to add the fqdn's for Office 365 but I have this sinking feeling this checkpoint firewall does not support wildcard fqdn's. It seems to do a reverse lookup on the IP that has no hope of working most of the time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also even for normal FQDN's it doesn't always work unless I have the firewall pointing to the same DNS server as the clients. I would of thought the firewall sees all dns requests as they pass through the firewall and the corresponding IP's returned to add to the rule set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then even when I use the same DNS servers sometimes on a basic FQDN, there are issues for those FQDN's with low TTLs. Does it not cache older DNS results to ensure the dns ttl window is not an issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Sep 2018 17:48:35 GMT</pubDate>
    <dc:creator>Bob_Bobson</dc:creator>
    <dc:date>2018-09-26T17:48:35Z</dc:date>
    <item>
      <title>have a sinking feeling that wildcard fqdn's are not supported...?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/have-a-sinking-feeling-that-wildcard-fqdn-s-are-not-supported/m-p/29719#M6072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;looking to add the fqdn's for Office 365 but I have this sinking feeling this checkpoint firewall does not support wildcard fqdn's. It seems to do a reverse lookup on the IP that has no hope of working most of the time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also even for normal FQDN's it doesn't always work unless I have the firewall pointing to the same DNS server as the clients. I would of thought the firewall sees all dns requests as they pass through the firewall and the corresponding IP's returned to add to the rule set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then even when I use the same DNS servers sometimes on a basic FQDN, there are issues for those FQDN's with low TTLs. Does it not cache older DNS results to ensure the dns ttl window is not an issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2018 17:48:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/have-a-sinking-feeling-that-wildcard-fqdn-s-are-not-supported/m-p/29719#M6072</guid>
      <dc:creator>Bob_Bobson</dc:creator>
      <dc:date>2018-09-26T17:48:35Z</dc:date>
    </item>
    <item>
      <title>Re: have a sinking feeling that wildcard fqdn's are not supported...?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/have-a-sinking-feeling-that-wildcard-fqdn-s-are-not-supported/m-p/29720#M6073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A better way to do this is with the Office 365 updatable objects available with R80.20, which was just released yesterday.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2018 17:46:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/have-a-sinking-feeling-that-wildcard-fqdn-s-are-not-supported/m-p/29720#M6073</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2018-09-27T17:46:50Z</dc:date>
    </item>
  </channel>
</rss>

