<?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 Issues with resolving Xsoar DNS Alias in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/issues-with-resolving-xsoar-dns-alias/m-p/513144#M106604</link>
    <description>&lt;P&gt;Hello, I am hoping someone here may be able to guide me. My company is using&amp;nbsp;&lt;SPAN&gt;Xsoar, and we are having an issue with resolving DNS alias for it. The servers resolve to an AWS url. Half the time it resolves the other half it does not. Even support.paloaltonetworks.com there is an issue resolving half the time. It is intermittent it seems. I looked up support.paloaltonetworks.com on mxtoolbox, and it can not find the record on one of its servers either. I am not sure what to do here or who I should open an issue with. Any guidance is appreciated.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 26 Aug 2022 17:41:58 GMT</pubDate>
    <dc:creator>QUARINTEEN</dc:creator>
    <dc:date>2022-08-26T17:41:58Z</dc:date>
    <item>
      <title>Issues with resolving Xsoar DNS Alias</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/issues-with-resolving-xsoar-dns-alias/m-p/513144#M106604</link>
      <description>&lt;P&gt;Hello, I am hoping someone here may be able to guide me. My company is using&amp;nbsp;&lt;SPAN&gt;Xsoar, and we are having an issue with resolving DNS alias for it. The servers resolve to an AWS url. Half the time it resolves the other half it does not. Even support.paloaltonetworks.com there is an issue resolving half the time. It is intermittent it seems. I looked up support.paloaltonetworks.com on mxtoolbox, and it can not find the record on one of its servers either. I am not sure what to do here or who I should open an issue with. Any guidance is appreciated.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2022 17:41:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/issues-with-resolving-xsoar-dns-alias/m-p/513144#M106604</guid>
      <dc:creator>QUARINTEEN</dc:creator>
      <dc:date>2022-08-26T17:41:58Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with resolving Xsoar DNS Alias</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/issues-with-resolving-xsoar-dns-alias/m-p/513161#M106613</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/194193"&gt;@QUARINTEEN&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Have you verified that it isn't limited to a single forwarder that you're using? It's possible that you and MXToolbox are hitting the same service that fails to resolve the FQDN when you were testing, and identifying that commonality would possibly at least tell you what's causing the issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2022 22:02:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/issues-with-resolving-xsoar-dns-alias/m-p/513161#M106613</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2022-08-26T22:02:55Z</dc:date>
    </item>
  </channel>
</rss>

