<?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: Asterisk Usage in Creating Domain Object in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219840#M36626</link>
    <description>&lt;P&gt;I have not tested that in some time, but it has to start with a . sign.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Sat, 06 Jul 2024 12:45:12 GMT</pubDate>
    <dc:creator>the_rock</dc:creator>
    <dc:date>2024-07-06T12:45:12Z</dc:date>
    <item>
      <title>Asterisk Usage in Creating Domain Object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219809#M36622</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;While creating Domain object in MDSM,&amp;nbsp;&lt;/SPAN&gt;Can I add A&lt;SPAN&gt;sterisk symbol in front of domain.&amp;nbsp; If I add will it work in rules?&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;Example:&amp;nbsp;&lt;/P&gt;&lt;P&gt;Object Name:&amp;nbsp; .*.powerbi.com&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rajesh.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2024 19:14:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219809#M36622</guid>
      <dc:creator>Cvr</dc:creator>
      <dc:date>2024-07-05T19:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: Asterisk Usage in Creating Domain Object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219814#M36623</link>
      <description>&lt;P&gt;No you cannot use * for both options. So if you enable FQDN or disable it you have to work with a dot (.) not with *&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Select&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="Menu_Options"&gt;FQDN&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In the object name, use the Fully Qualified&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_BladesFeatures.tp_domain variable"&gt;Domain&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Name (FQDN). Use the format .&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;x.y.z&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(with a dot "." before the FQDN). For example, if you use .&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;&lt;A href="http://www.example.com" target="_blank"&gt;www.example.com&lt;/A&gt;&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;then the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_Other.tp_gwcap variable"&gt;Gateway&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;matches&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;&lt;A href="http://www.example.com" target="_blank"&gt;www.example.com&lt;/A&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;This option is supported for&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_Versions.r_hugo variable"&gt;R80.10&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and higher, and is the default. It is more accurate and faster than the non-FQDN option.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_Other.tp_sgate variable"&gt;&lt;A class="MCTextPopup MCTextPopupHotSpot MCTextPopupHotSpot_ #text MCTextPopup_Closed" role="button" href="https://sc1.checkpoint.com/documents/R81.10/SmartConsole_OLH/EN/Topics-OLH/aye9E1MOabS0WJ8uuPMh_g2.htm?cshid=aye9E1MOabS0WJ8uuPMh_g2#" data-mc-state="closed" data-aria-describedby="97571b4d-625b-4f7e-891a-6f06572e5919" target="_blank"&gt;Security Gateway&amp;nbsp;&lt;/A&gt;&lt;/SPAN&gt;looks up the FQDN with a direct DNS query, and uses the result in the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_Other.tp_rule variable"&gt;&lt;A class="MCTextPopup MCTextPopupHotSpot MCTextPopupHotSpot_ #text MCTextPopup_Closed" role="button" href="https://sc1.checkpoint.com/documents/R81.10/SmartConsole_OLH/EN/Topics-OLH/aye9E1MOabS0WJ8uuPMh_g2.htm?cshid=aye9E1MOabS0WJ8uuPMh_g2#" data-mc-state="closed" data-aria-describedby="54cef798-4caa-44cf-9733-e58fa39c1e7b" target="_blank"&gt;Rule Base&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;This option supports&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_BladesFeatures.tp_sxl variable"&gt;&lt;A class="MCTextPopup MCTextPopupHotSpot MCTextPopupHotSpot_ #text MCTextPopup_Closed" role="button" href="https://sc1.checkpoint.com/documents/R81.10/SmartConsole_OLH/EN/Topics-OLH/aye9E1MOabS0WJ8uuPMh_g2.htm?cshid=aye9E1MOabS0WJ8uuPMh_g2#" data-mc-state="closed" data-aria-describedby="3df4eae3-3f66-4701-a7bd-feb5dd3a9486" target="_blank"&gt;SecureXL&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Accept templates. Using domain objects with this option in a&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="MCTextPopup MCTextPopupHotSpot MCTextPopupHotSpot_ #text MCTextPopup_Closed" role="button" href="https://sc1.checkpoint.com/documents/R81.10/SmartConsole_OLH/EN/Topics-OLH/aye9E1MOabS0WJ8uuPMh_g2.htm?cshid=aye9E1MOabS0WJ8uuPMh_g2#" data-mc-state="closed" data-aria-describedby="8c40c796-d5a2-4233-8393-57c13884258d" target="_blank"&gt;rule&amp;nbsp;&lt;/A&gt;has no effect on the performance of the rule, or of the rules that come after it.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Clear&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="Menu_Options"&gt;FQDN&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This option enforces the domain and its sub-domains. In the object name, use the format .&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;x.y&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;for the name. For example, use .&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;example.com&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or .&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;example.co.uk&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;for the name. If you use .&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;example.com&lt;/CODE&gt;, then the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_Other.tp_gwcap variable"&gt;Gateway&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;matches&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;&lt;A href="http://www.example.com" target="_blank"&gt;www.example.com&lt;/A&gt;&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;support.example.com&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_Other.tp_gwcap variable"&gt;Gateway&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;does the name resolution using DNS reverse lookups, which can be inaccurate. The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_Other.tp_gwcap variable"&gt;Gateway&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;uses the result in the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="mc-variable Vars_Other.tp_rule variable"&gt;Rule Base&lt;/SPAN&gt;, and caches the result to use again.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2024 20:15:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219814#M36623</guid>
      <dc:creator>Lesley</dc:creator>
      <dc:date>2024-07-05T20:15:43Z</dc:date>
    </item>
    <item>
      <title>Re: Asterisk Usage in Creating Domain Object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219840#M36626</link>
      <description>&lt;P&gt;I have not tested that in some time, but it has to start with a . sign.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Sat, 06 Jul 2024 12:45:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219840#M36626</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-07-06T12:45:12Z</dc:date>
    </item>
    <item>
      <title>Re: Asterisk Usage in Creating Domain Object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219841#M36627</link>
      <description>&lt;P&gt;Here is the sk&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk120633" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk120633&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Sat, 06 Jul 2024 13:10:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219841#M36627</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-07-06T13:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: Asterisk Usage in Creating Domain Object</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219842#M36628</link>
      <description>&lt;P&gt;Also, for the context, that option for fqdn also matters, depending on exactly what you are accessing&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/114071"&gt;@Cvr&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Sat, 06 Jul 2024 14:13:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Asterisk-Usage-in-Creating-Domain-Object/m-p/219842#M36628</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-07-06T14:13:27Z</dc:date>
    </item>
  </channel>
</rss>

