<?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: How to configure pool.ntp.org or us.pool.ntp.org as ntp server in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-to-configure-pool-ntp-org-or-us-pool-ntp-org-as-ntp-server/m-p/1238379#M6303</link>
    <description>&lt;P&gt;it indeed looks like you keep getting 4 random IP addresses each time you resolve the FQDN&lt;/P&gt;
&lt;P&gt;- stick to 2 of the IPs you receive and put those in your NTP config&lt;/P&gt;
&lt;P&gt;- pick a different NTP with more predictable IP addresses&lt;/P&gt;
&lt;P&gt;- allow all outbound NTP from your management interface&lt;/P&gt;
&lt;P&gt;- run an internal NTP server&lt;/P&gt;</description>
    <pubDate>Fri, 19 Sep 2025 12:04:19 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2025-09-19T12:04:19Z</dc:date>
    <item>
      <title>How to configure pool.ntp.org or us.pool.ntp.org as ntp server</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-to-configure-pool-ntp-org-or-us-pool-ntp-org-as-ntp-server/m-p/1238207#M6298</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I configured them both using fqdn on the security policy with source as firewall management interface but ntp status shows rejected. How do I fix this. Please help&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;All services to the internet use management interface&lt;/P&gt;&lt;P&gt;DNS&amp;nbsp; configured 1.1.1.1 and 8.8.8.8&lt;/P&gt;&lt;P&gt;Firewall can ping 1.1.1.1 and&amp;nbsp;8.8.8.8&lt;/P&gt;&lt;P&gt;Allowed application ntp and ntp base&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I checked the monitor tab I see two times a traffic has hit the rule and firewall has allowed the traffic and rest all it has denied. My theory is that the IP address of&amp;nbsp;&lt;/SPAN&gt;&lt;A class="" href="http://pool.ntp.org/" target="_blank" rel="noopener nofollow noreferrer ugc"&gt;pool.ntp.org&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;keeps changing everytime so if firewall does not have the IP address in its DNS cache, it would drop the traffic, please advise if I am wrong&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Sep 2025 11:47:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-to-configure-pool-ntp-org-or-us-pool-ntp-org-as-ntp-server/m-p/1238207#M6298</guid>
      <dc:creator>ciscojuniperf5</dc:creator>
      <dc:date>2025-09-17T11:47:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure pool.ntp.org or us.pool.ntp.org as ntp server</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-to-configure-pool-ntp-org-or-us-pool-ntp-org-as-ntp-server/m-p/1238379#M6303</link>
      <description>&lt;P&gt;it indeed looks like you keep getting 4 random IP addresses each time you resolve the FQDN&lt;/P&gt;
&lt;P&gt;- stick to 2 of the IPs you receive and put those in your NTP config&lt;/P&gt;
&lt;P&gt;- pick a different NTP with more predictable IP addresses&lt;/P&gt;
&lt;P&gt;- allow all outbound NTP from your management interface&lt;/P&gt;
&lt;P&gt;- run an internal NTP server&lt;/P&gt;</description>
      <pubDate>Fri, 19 Sep 2025 12:04:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-to-configure-pool-ntp-org-or-us-pool-ntp-org-as-ntp-server/m-p/1238379#M6303</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2025-09-19T12:04:19Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure pool.ntp.org or us.pool.ntp.org as ntp server</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-to-configure-pool-ntp-org-or-us-pool-ntp-org-as-ntp-server/m-p/1238480#M6309</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Firstly, you cannot configure the management interface in a policy since it is not part of the data plane. Secondly, test connectivity by pinging &lt;CODE data-start="203" data-end="217"&gt;pool.ntp.org&lt;/CODE&gt; from the firewall. From what you have explained, I think you need to check the routes after the management interface (on switch/router). Alternatively, you can perform a tcpdump on the management interface to see if packets are being sent or received.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://docs.paloaltonetworks.com/ngfw/administration/monitoring/take-packet-captures/take-a-packet-capture-on-the-management-interface" target="_blank"&gt;https://docs.paloaltonetworks.com/ngfw/administration/monitoring/take-packet-captures/take-a-packet-capture-on-the-management-interface&lt;/A&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Sep 2025 07:21:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-to-configure-pool-ntp-org-or-us-pool-ntp-org-as-ntp-server/m-p/1238480#M6309</guid>
      <dc:creator>f.kuecuek</dc:creator>
      <dc:date>2025-09-22T07:21:36Z</dc:date>
    </item>
  </channel>
</rss>

