<?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: ZBF with dynamic DNS names in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4773581#M1097709</link>
    <description>&lt;P&gt;policy-map is using class-map which can use&amp;nbsp;&lt;BR /&gt;protocol &amp;lt;&amp;lt;- this as we see above not suitable for your case&amp;nbsp;&lt;BR /&gt;ACL &amp;lt;&amp;lt;- here you can use ACL to permit/deny hostname&amp;nbsp;&amp;nbsp;&lt;A href="https://blog.ipspace.net/2008/11/using-hostnames-in-ip-access-lists.html" target="_blank"&gt;https://blog.ipspace.net/2008/11/using-hostnames-in-ip-access-lists.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;try using ACL for hostname as link above with class-map.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;hope this help you.&amp;nbsp;&lt;BR /&gt;thanks&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 12 Feb 2023 20:54:02 GMT</pubDate>
    <dc:creator>MHM Cisco World</dc:creator>
    <dc:date>2023-02-12T20:54:02Z</dc:date>
    <item>
      <title>ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767499#M1097425</link>
      <description>&lt;P&gt;I am looking for explenation/documentation what actually happens when i implement something like this :&amp;nbsp;&lt;/P&gt;&lt;P&gt;parameter-map type protocol-info example_allow&lt;BR /&gt;server name example.com&lt;BR /&gt;server name *.example.com&lt;BR /&gt;server name &lt;A href="http://www.example.com" target="_blank" rel="noopener"&gt;www.example.com&lt;/A&gt;&lt;BR /&gt;class-map type inspect match-any example_allow&lt;BR /&gt;description allowing certain websites&lt;BR /&gt;match protocol http example_allow&lt;BR /&gt;match protocol https example_allow&lt;BR /&gt;class type inspect example_allow&lt;BR /&gt;inspect&lt;/P&gt;&lt;P&gt;+ dns coniguration with ip domain lookup enabled&amp;nbsp;&lt;/P&gt;&lt;P&gt;i am putting it on policymap , zones everything configured correctly and acctually i would like to achieve that people who goes from zone internal2external lets say can only reach this example.com website. I believe that :&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;show parameter-map type protocol-info dns-cache zone-pair internal2external&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;will show me maping of dns with ip ...&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;So quetion, is it working in that way ? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; i cannot find details whats the influance on performance , how often lookup will be executed, if it somehow may cause longer delay .. is it basic feature or it require something additional in compare to basic l3/l4 zbf..&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Many thanks in advance for sheding some light on this topic.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;p.s. currently we use only static entries - access lists with ip addresses what for internal services lets say is fine but for dynamic, internet... not scalable at all&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 14:57:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767499#M1097425</guid>
      <dc:creator>kzajdlew</dc:creator>
      <dc:date>2023-02-02T14:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767506#M1097426</link>
      <description>&lt;P&gt;can you more elaborate ?&lt;BR /&gt;DNS work with IP&amp;nbsp;&lt;BR /&gt;ZoneFirewall can inspect :-&lt;BR /&gt;1- IP via ACL&amp;nbsp;&lt;BR /&gt;2- Protocol&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;so even if DNS change IP you can still use protocol instead to inspect the traffic.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 15:24:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767506#M1097426</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-02T15:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767589#M1097440</link>
      <description>&lt;P&gt;I am not sure if i understood you correctly. In short i am looking for solution where i could replace static ip addresses in access lists with dynamic dns objects e.g putting teams.microsoft.com instead of using mutiplce ip addresses like&amp;nbsp;52.113.194.132 leading to teams..&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;p.s. i am beginner with zbf &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 16:22:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767589#M1097440</guid>
      <dc:creator>kzajdlew</dc:creator>
      <dc:date>2023-02-02T16:22:06Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767593#M1097441</link>
      <description>&lt;P&gt;what TCP/UDP you inspect ?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 16:29:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767593#M1097441</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-02T16:29:25Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767681#M1097442</link>
      <description>&lt;P&gt;as example :&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;tcp eq 443&lt;BR /&gt;tcp eq www&lt;BR /&gt;udp eq 3478&lt;BR /&gt;udp eq 3479&lt;BR /&gt;udp eq 3480&lt;BR /&gt;udp eq 3481&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 18:06:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767681#M1097442</guid>
      <dc:creator>kzajdlew</dc:creator>
      <dc:date>2023-02-02T18:06:43Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767693#M1097444</link>
      <description>&lt;P&gt;I will share config with you&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 18:38:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767693#M1097444</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-02T18:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767712#M1097445</link>
      <description>&lt;P&gt;this simple lab, R1 config with ZoneFirewall but I use Protocol not IP for inspection.&lt;BR /&gt;I allow only port telnet and ICMP.&lt;BR /&gt;I try telnet from R3 to R2 success&lt;BR /&gt;I try ping from R3 to R2 success&amp;nbsp;&lt;BR /&gt;I try traceroute from R3 to R2 failed, because the traceroute is not allow for inspection.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kjhkhjkhjkhjkhjkhj.png" style="width: 597px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/175609i1A8EC01DEF0843DC/image-size/large?v=v2&amp;amp;px=999" role="button" title="kjhkhjkhjkhjkhjkhj.png" alt="kjhkhjkhjkhjkhjkhj.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;class-map type inspect match-any Port&lt;BR /&gt;&lt;FONT color="#00FF00"&gt;&lt;STRONG&gt;match protocol telnet&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#00FF00"&gt;&lt;STRONG&gt;match protocol icmp&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;policy-map type inspect policy&lt;BR /&gt;class type inspect Port&lt;BR /&gt;inspect&lt;BR /&gt;class class-default&lt;BR /&gt;drop log&lt;BR /&gt;!&lt;BR /&gt;zone security IN&lt;BR /&gt;zone security OUT&lt;BR /&gt;zone-pair security IN-to-OUT source IN destination OUT&lt;BR /&gt;service-policy type inspect policy&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 19:08:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767712#M1097445</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-02T19:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767727#M1097447</link>
      <description>&lt;P&gt;Unfortunately this is not what i was looking for. Maybe i described it wrongly but i am not interested in services/ports/protocols but "destination objects".&lt;/P&gt;&lt;P&gt;For example in your lab let say that router r2 has a dns name r2.test.com and webservice enabled.. i would like to have posibility to create a rule to allow http only to domain *.test.com... so for instance from r3 i should able to http to this r2 even though his ip could change but name would remian same..&amp;nbsp; so r1 should make a dns query from time to time to keep it in dns cache and dynamicly put in firewall rule&lt;/P&gt;&lt;P&gt;example of domain object in checkpoint security gateway :&amp;nbsp;&lt;/P&gt;&lt;H1&gt;Domains&lt;/H1&gt;&lt;P&gt;A&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Domain&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;object lets you define a host or DNS domain by its name only. It is not necessary to have the IP address of the site.&lt;/P&gt;&lt;P&gt;You can use the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Domain&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;object in the source and destination columns of an&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Access Control&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Policy.&lt;/P&gt;&lt;P&gt;You can configure a&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Domain&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;object in two ways:&lt;/P&gt;&lt;P&gt;-Select&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&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=""&gt;Domain&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Name (FQDN). Use the format .x.y.z&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(with a dot "." before the FQDN). For example, if you use .&lt;A href="http://www.example.com&amp;nbsp;" target="_blank"&gt;www.example.com&amp;nbsp;&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;then the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Gateway&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;matches&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="http://www.example.com&amp;nbsp;" target="_blank"&gt;www.example.com&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This option is supported for&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&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;P&gt;&lt;SPAN&gt;Security Gateway&amp;nbsp;&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=""&gt;Rule Base&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;-Clear&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;FQDN&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;This option enforces the domain and its sub-domains. In the object name, use the format .x.y&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;for the name. For example, use .example.com&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or .example.co.uk&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;for the name. If you use .example.com, then the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Gateway&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;matches&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="http://www.example.com&amp;nbsp;" target="_blank"&gt;www.example.com&amp;nbsp;&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;support.example.com&lt;/P&gt;&lt;P&gt;The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&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=""&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=""&gt;Rule Base&lt;/SPAN&gt;, and caches the result to use again.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 19:57:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767727#M1097447</guid>
      <dc:creator>kzajdlew</dc:creator>
      <dc:date>2023-02-02T19:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767730#M1097448</link>
      <description>&lt;P&gt;Now I get it, I will check solutionm, update you soon&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 19:59:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767730#M1097448</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-02T19:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767732#M1097449</link>
      <description>&lt;P&gt;ok, thank you very much&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 20:00:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4767732#M1097449</guid>
      <dc:creator>kzajdlew</dc:creator>
      <dc:date>2023-02-02T20:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4772136#M1097644</link>
      <description>&lt;P&gt;so far i ve not received a feedback which will help me with this topic, anything would be welcome&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2023 14:14:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4772136#M1097644</guid>
      <dc:creator>kzajdlew</dc:creator>
      <dc:date>2023-02-09T14:14:55Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4773581#M1097709</link>
      <description>&lt;P&gt;policy-map is using class-map which can use&amp;nbsp;&lt;BR /&gt;protocol &amp;lt;&amp;lt;- this as we see above not suitable for your case&amp;nbsp;&lt;BR /&gt;ACL &amp;lt;&amp;lt;- here you can use ACL to permit/deny hostname&amp;nbsp;&amp;nbsp;&lt;A href="https://blog.ipspace.net/2008/11/using-hostnames-in-ip-access-lists.html" target="_blank"&gt;https://blog.ipspace.net/2008/11/using-hostnames-in-ip-access-lists.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;try using ACL for hostname as link above with class-map.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;hope this help you.&amp;nbsp;&lt;BR /&gt;thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 12 Feb 2023 20:54:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4773581#M1097709</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-12T20:54:02Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4773852#M1097716</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;This seems to be static and without any scalibilty = dns lookup take place probably only at the begining and putting ip in place. I am looking for somethng dynamic&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 08:29:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4773852#M1097716</guid>
      <dc:creator>kzajdlew</dc:creator>
      <dc:date>2023-02-13T08:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4774553#M1097747</link>
      <description>&lt;P&gt;but if your DNS server return time TTL then the ZFW will ask hostname in periodic time&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 00:41:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4774553#M1097747</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-14T00:41:15Z</dc:date>
    </item>
    <item>
      <title>Re: ZBF with dynamic DNS names</title>
      <link>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4775277#M1097781</link>
      <description>&lt;P&gt;but what if DNS loabalnce traffic between multiple ips ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 13:21:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbf-with-dynamic-dns-names/m-p/4775277#M1097781</guid>
      <dc:creator>kzajdlew</dc:creator>
      <dc:date>2023-02-14T13:21:19Z</dc:date>
    </item>
  </channel>
</rss>

