<?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 Global Protect on MacOS (TYPE65 dns queries) in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-on-macos-type65-dns-queries/m-p/589084#M5440</link>
    <description>&lt;P&gt;While troubleshooting a failing &lt;LI-PRODUCT title="GlobalProtect" id="GlobalProtect"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;update on my own machine, I checked the DNS requests made by the Global Protect updater. And noticed that it's not making type A requests, but instead uses TYPE65 (aka HTTPS or&lt;SPAN&gt;draft spec RFC 9460)&lt;/SPAN&gt;&amp;nbsp;requests. My internal DNS server don't have the option of hosting this type of record. The update fails as after two attempts per upstream DNS server the updater appears to give up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has anyone encountered anything like this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;TYPE65 is pre-standard but Apple has adopted this in MacOS. As for Global Protect (v6.2.2) I don't know if it or my OS is making it use a TYPE65 query. Fine if a system wants to try TYPE65 first, but for goodness sake, fall back to A/AAAA if it fails.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Another consequence of TYPE65 queries:&amp;nbsp;&lt;A href="https://discussions.apple.com/thread/252092927?sortBy=best" target="_blank"&gt;https://discussions.apple.com/thread/252092927?sortBy=best&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jun 2024 16:40:41 GMT</pubDate>
    <dc:creator>dmgeurts</dc:creator>
    <dc:date>2024-06-07T16:40:41Z</dc:date>
    <item>
      <title>Global Protect on MacOS (TYPE65 dns queries)</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-on-macos-type65-dns-queries/m-p/589084#M5440</link>
      <description>&lt;P&gt;While troubleshooting a failing &lt;LI-PRODUCT title="GlobalProtect" id="GlobalProtect"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;update on my own machine, I checked the DNS requests made by the Global Protect updater. And noticed that it's not making type A requests, but instead uses TYPE65 (aka HTTPS or&lt;SPAN&gt;draft spec RFC 9460)&lt;/SPAN&gt;&amp;nbsp;requests. My internal DNS server don't have the option of hosting this type of record. The update fails as after two attempts per upstream DNS server the updater appears to give up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has anyone encountered anything like this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;TYPE65 is pre-standard but Apple has adopted this in MacOS. As for Global Protect (v6.2.2) I don't know if it or my OS is making it use a TYPE65 query. Fine if a system wants to try TYPE65 first, but for goodness sake, fall back to A/AAAA if it fails.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Another consequence of TYPE65 queries:&amp;nbsp;&lt;A href="https://discussions.apple.com/thread/252092927?sortBy=best" target="_blank"&gt;https://discussions.apple.com/thread/252092927?sortBy=best&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 16:40:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-on-macos-type65-dns-queries/m-p/589084#M5440</guid>
      <dc:creator>dmgeurts</dc:creator>
      <dc:date>2024-06-07T16:40:41Z</dc:date>
    </item>
  </channel>
</rss>

