<?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: What triggers DNS Records update for dynatrace-managed.com? in Cloud platforms</title>
    <link>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176222#M691</link>
    <description>&lt;P&gt;Usually after the restore new cluster nodes should recognize the situation and the domain should be updated automatically if connection to Mission Control is OK.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Nov 2021 11:16:54 GMT</pubDate>
    <dc:creator>Radoslaw_Szulgo</dc:creator>
    <dc:date>2021-11-22T11:16:54Z</dc:date>
    <item>
      <title>What triggers DNS Records update for dynatrace-managed.com?</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176182#M689</link>
      <description>&lt;P&gt;I am in the midst of migrating a Dynatrace Managed cluster from on-prem data centre to Azure cloud VM.&lt;/P&gt;
&lt;P&gt;I am using "Cluster backup and restore" method as depicted in documentation.&lt;/P&gt;
&lt;P&gt;When the restoration completed, DNS entry for the dynatrace-managed URL got updated to Azure VM's IP address.&lt;/P&gt;
&lt;P&gt;However after about 3 hours, I had to fall back to using the existing on-prem Dynatrace Managed. Dynatrace services on Azure VM was shut down but DNS records for the dynatrace-managed.com URL stay stuck to the Azure VM's IP.&lt;/P&gt;
&lt;P&gt;Eventually I shut down the Azure VM OS itself, and then only DNS records update to the IP where Dynatrace Managed is running at.&lt;/P&gt;
&lt;P&gt;I'm pretty curious, what are the triggers for DNS record changes for dynatrace-managed.com? It doesn't require existing on-prem servers to be shutdown to get its IP updated to Azure, but it isn't the same case in reverse.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 08:14:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176182#M689</guid>
      <dc:creator>mengsuan_koe1</dc:creator>
      <dc:date>2021-11-22T08:14:35Z</dc:date>
    </item>
    <item>
      <title>Re: What triggers DNS Records update for dynatrace-managed.com?</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176183#M690</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/39409"&gt;@mengsuan_koe1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please have a look at the below link:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/configuration/dns-configuration-in-managed/" target="_blank" rel="noopener"&gt;https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/configuration/dns-configuration-in-managed/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Babar Qayyum&lt;/P&gt;</description>
      <pubDate>Sun, 21 Nov 2021 06:56:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176183#M690</guid>
      <dc:creator>Babar_Qayyum</dc:creator>
      <dc:date>2021-11-21T06:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: What triggers DNS Records update for dynatrace-managed.com?</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176222#M691</link>
      <description>&lt;P&gt;Usually after the restore new cluster nodes should recognize the situation and the domain should be updated automatically if connection to Mission Control is OK.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 11:16:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176222#M691</guid>
      <dc:creator>Radoslaw_Szulgo</dc:creator>
      <dc:date>2021-11-22T11:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: What triggers DNS Records update for dynatrace-managed.com?</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176235#M692</link>
      <description>&lt;P&gt;Yeah, I can see that when a cluster node is restored, the DNS for dynatrace-managed.com gets updated promptly.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I guess my scenario was out-of-the-norm because I had to revert back to the old cluster, and I guess that is when DNS is not switching back to that old cluster promptly.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 13:23:20 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176235#M692</guid>
      <dc:creator>mengsuan_koe1</dc:creator>
      <dc:date>2021-11-22T13:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: What triggers DNS Records update for dynatrace-managed.com?</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176243#M693</link>
      <description>&lt;P&gt;that's very probable&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 13:58:31 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/What-triggers-DNS-Records-update-for-dynatrace-managed-com/m-p/176243#M693</guid>
      <dc:creator>Radoslaw_Szulgo</dc:creator>
      <dc:date>2021-11-22T13:58:31Z</dc:date>
    </item>
  </channel>
</rss>

