https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-DNS-NAM-Monitors/ta-p/300483 <H2>Summary</H2> <P>This article focuses on <STRONG>Dynatrace Synthetic Monitoring</STRONG>, specifically <STRONG>Network Availability Monitors (NAM) using DNS</STRONG>, and explains why a <STRONG>private Synthetic location may not be selectable</STRONG> when creating DNS monitors.</P> <P>It helps you understand the <STRONG>platform prerequisites and system‑level dependencies</STRONG> that determine whether <STRONG>DNS monitoring</STRONG> is available from a private location, and how to validate DNS availability using <STRONG>ActiveGate diagnostics and local DNS checks</STRONG>.</P> <P>&nbsp;</P> <P><LI-TOC indent="15" liststyle="disc" maxheadinglevel="3"></LI-TOC></P> <H2>&nbsp;</H2> <H2>Problem</H2> <P>After deploying <STRONG>Synthetic‑enabled ActiveGates</STRONG> and assigning them to a new <STRONG>private Synthetic location</STRONG>, the location appears as <STRONG>Not supported</STRONG> when attempting to create a <STRONG>DNS Network Availability Monitor</STRONG>.</P> <H3>&nbsp;</H3> <H3>In the Dynatrace UI</H3> <P>You may observe one or more of the following:</P> <UL> <LI>In <STRONG>Synthetic → Private locations</STRONG>, the private location shows a <STRONG>Compatibility health alert</STRONG></LI> <LI><STRONG>Network Availability (DNS)</STRONG> is missing from the available monitor types under<BR /><STRONG>Classic Settings → Web and mobile monitoring → Private Synthetic locations → Edit location</STRONG></LI> <LI>The private location is marked as <STRONG>Not supported</STRONG>, with a message indicating that the location is not configured to execute this type of monitor</LI> </UL> <H2>&nbsp;</H2> <H2>Evidence in ActiveGate logs</H2> <P>The ActiveGate diagnostic logs (<CODE>vuc-status.log</CODE>) indicate that DNS is unavailable, even though other multi‑protocol capabilities may still be operational:</P> <LI-CODE lang="markup">2026-06-09T07:29:46,227Z [DiagnosticResultsHolder] multi-protocol = `DiagnosticResultsChangedEvent[moduleName=MULTIPROTOCOL, diagnosticCasesResult=DiagnosticCasesResult[isOperational=true, cases={MULTIPROTOCOL_TCP=DiagnosticCaseDetail[isAvailable=true], MULTIPROTOCOL_DNS=DiagnosticCaseDetail[isAvailable=false], MULTIPROTOCOL_ICMP=DiagnosticCaseDetail[isAvailable=true]}]]`</LI-CODE> <P>When <CODE>MULTIPROTOCOL_DNS</CODE> is reported as <STRONG>isAvailable=false</STRONG>, DNS NAM monitors are automatically disabled for the private location.</P> <P>For information on finding the log see&nbsp;<A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/Useful-Synthetic-ActiveGate-logs/ta-p/214478" target="_blank">Useful Synthetic ActiveGate logs</A></P> <P>&nbsp;</P> <H2>Troubleshooting steps</H2> <P>Use the following steps to determine whether the limitation is related to <STRONG>Dynatrace configuration</STRONG> or to <STRONG>host‑level DNS resolution</STRONG>.</P> <H3>&nbsp;</H3> <H3>1. Review ActiveGate diagnostic results</H3> <P>On the ActiveGate host, check the <CODE>vuc-status.log</CODE> and confirm whether DNS is reported as unavailable:</P> <P><SPAN>MULTIPROTOCOL_DNS=DiagnosticCaseDetail[isAvailable=false]</SPAN></P> <P>If DNS is unavailable at this level, the private Synthetic location cannot support DNS NAM monitors.</P> <H3>&nbsp;</H3> <H3>2. Understand how DNS availability is validated</H3> <DIV> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol">DNS Network Availability Monitors rely on the <STRONG>host operating system’s DNS resolver</STRONG>.<BR />When applicable, entries defined in the <STRONG><CODE>/etc/hosts</CODE> file</STRONG> are also used for hostname resolution.</DIV> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol">Important characteristics:</DIV> <UL> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">The ActiveGate uses the <STRONG>machine’s configured DNS settings</STRONG></LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"><STRONG><CODE>/etc/hosts</CODE></STRONG> is consulted when relevant hostnames are defined there</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">No Dynatrace‑specific DNS server is bundled with the ActiveGate</LI> <LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf">If DNS resolution fails at the OS level, <STRONG>DNS execution is disabled automatically</STRONG></LI> </UL> <DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol">This means that DNS availability for a private Synthetic location is determined entirely by the <STRONG>host’s ability to resolve hostnames</STRONG>, using standard operating system resolution mechanisms.</DIV> </DIV> <H3>&nbsp;</H3> <H3>3. Verify local DNS resolution on the ActiveGate host</H3> <H4><span class="lia-unicode-emoji" title=":magnifying_glass_tilted_right:">🔎</span> Use&nbsp;<CODE>nslookup</CODE> for basic DNS validation</H4> <P>Run the following command directly on the ActiveGate host:</P> <LI-CODE lang="markup">nslookup -debug -type=A localhost</LI-CODE> <P>This check validates that:</P> <UL> <LI>The local DNS resolver is reachable</LI> <LI>DNS queries are processed successfully</LI> <LI>The system can resolve hostnames using its configured DNS servers</LI> </UL> <P>If this command fails, DNS NAM monitors will not be enabled for the private Synthetic location.</P> <P>&nbsp;</P> <H4><span class="lia-unicode-emoji" title=":magnifying_glass_tilted_right:">🔎</span>&nbsp;<SPAN>Use </SPAN><CODE>dig</CODE><SPAN> for detailed DNS validation</SPAN></H4> <DIV> <P>In addition to basic DNS checks, you can use the <CODE>dig</CODE> command on the ActiveGate host to validate DNS resolution more precisely.</P> <P><span class="lia-unicode-emoji" title=":backhand_index_pointing_right:">👉</span> Run a simple lookup:</P> <DIV class="___77lcry0 f10pi13n"> <DIV class="___1hewfwb f10pi13n f7oukh6 f5p0z4x" tabindex="0" role="group" aria-label="Code Preview"> <DIV class="fui-FluentProvider codeBlock-5480fui-FluentProviderrp ___1jk74h0 fzk5nv6 f6n0el9 f7x6x6c f1a9mlr7 flj889f f13g0yyb ffzn0d2" dir="ltr" data-testid="ComponentFluentProviderId"> <DIV class="scriptor-component-code-block scriptor-codeblock-virtualized ___sakztz0 fonrc96 fbwmw8f fk8brrf fssjx5q f11d9hfk f1rkeeuc fukujjm f1uhbleq f1j8h10f f1dcxf0u fhswmqe f1gsf85u fh8rik3 f1jl54mw f1w257bn f1c6ju7g fwfsotv f1ndaetk fg8ocxh fvbf5p7" tabindex="-1"> <DIV class="___4ll5qn0 fonrc96"> <DIV class="r14iuplo fui-AriaLive__assertive" aria-live="assertive"><LI-CODE lang="markup">dig &lt;TARGET_DOMAIN&gt;</LI-CODE></DIV> </DIV> <DIV class="scriptor-code-scroll-proxy"> <DIV>&nbsp;</DIV> </DIV> </DIV> </DIV> </DIV> </DIV> <P><span class="lia-unicode-emoji" title=":backhand_index_pointing_right:">👉</span> This allows you to:</P> <UL> <LI>Verify that the domain resolves correctly from the ActiveGate host</LI> <LI>Confirm the returned IP address(es)</LI> <LI>Check response status (for example <CODE>NOERROR</CODE>, <CODE>NXDOMAIN</CODE>, or timeout)</LI> </UL> <P><span class="lia-unicode-emoji" title=":backhand_index_pointing_right:">👉</span> For more targeted testing, you can:</P> <DIV class="___77lcry0 f10pi13n"> <DIV class="___1hewfwb f10pi13n f7oukh6 f5p0z4x" tabindex="0" role="group" aria-label="Code Preview"> <DIV class="fui-FluentProvider codeBlock-2970fui-FluentProviderr12 ___1jk74h0 fzk5nv6 f6n0el9 f7x6x6c f1a9mlr7 flj889f f13g0yyb ffzn0d2" dir="ltr" data-testid="ComponentFluentProviderId"> <DIV class="scriptor-component-code-block scriptor-codeblock-virtualized ___sakztz0 fonrc96 fbwmw8f fk8brrf fssjx5q f11d9hfk f1rkeeuc fukujjm f1uhbleq f1j8h10f f1dcxf0u fhswmqe f1gsf85u fh8rik3 f1jl54mw f1w257bn f1c6ju7g fwfsotv f1ndaetk fg8ocxh fvbf5p7" tabindex="-1"> <DIV class="___4ll5qn0 fonrc96"> <DIV class="r14iuplo fui-AriaLive__assertive" aria-live="assertive"><LI-CODE lang="markup">dig &lt;TARGET_DOMAIN&gt; A dig &lt;TARGET_DOMAIN&gt; @&lt;DNS_SERVER_IP&gt;</LI-CODE></DIV> </DIV> <DIV class="scriptor-code-scroll-proxy"> <DIV>&nbsp;</DIV> <DIV> <DIV>If <CODE>dig</CODE> fails while other connectivity tests succeed, this confirms the issue is DNS-specific and explains why the ActiveGate reports <CODE>MULTIPROTOCOL_DNS = isAvailable=false</CODE>.</DIV> <DIV>&nbsp;</DIV> </DIV> </DIV> </DIV> </DIV> </DIV> </DIV> </DIV> <H3>4. Check system‑level DNS configuration</H3> <P>Confirm that the ActiveGate host has:</P> <UL> <LI>Valid DNS servers configured (for example, in <CODE>/etc/resolv.conf</CODE> on Linux)</LI> <LI>No firewall or security tooling blocking DNS traffic</LI> <LI>No container or sandbox restrictions preventing access to the system resolver</LI> </UL> <H2>&nbsp;</H2> <H2>Resolution</H2> <P><STRONG>DNS availability in a private Synthetic location depends entirely on the underlying host’s ability to perform DNS resolution.</STRONG></P> <P>If DNS resolution is not functional at the system level:</P> <UL> <LI><CODE>MULTIPROTOCOL_DNS</CODE> is marked as unavailable</LI> <LI>The private Synthetic location is marked as <STRONG>Not supported</STRONG> for DNS monitoring</LI> </UL> <P>Once DNS resolution is restored on the host:</P> <UL> <LI>The ActiveGate automatically reports DNS as available</LI> <LI>The private Synthetic location updates its compatibility status</LI> <LI>DNS NAM monitors become selectable without additional Dynatrace configuration</LI> </UL> <H2>&nbsp;</H2> <H2>After resolving the cause of the failure</H2> <P>After DNS is reported as available:</P> <UL> <LI>Verify that <STRONG>DNS</STRONG> appears as a supported capability for the private location</LI> <LI>Create a <STRONG>DNS Network Availability Monitor</STRONG></LI> <LI>Confirm successful execution from the private Synthetic location</LI> </UL> <H2>&nbsp;</H2> <H2>What’s next</H2> <P><SPAN>If none of the previous steps resolved the issue, open a chat and provide the Support Archive from the ActiveGate with the troubleshooting steps you have already completed.</SPAN></P> <P>&nbsp;</P> <H3><STRONG>Related reading</STRONG></H3> <P><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp; <A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-on-grail/synthetic-app/private-locations/manage-private-locations#health-status" target="_blank" rel="noopener noreferrer">Manage Private locations</A></P> <DIV> <P><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp;<SPAN>&nbsp;</SPAN><A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-on-grail/synthetic-app/private-locations/requirements-for-private-synthetic#operating-system-requirements" target="_blank" rel="noopener noreferrer">Requirements for private locations</A></P> </DIV> <P><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp;<SPAN>&nbsp;</SPAN><A href="https://docs.dynatrace.com/docs/shortlink/containerized-locations#nam-monitors-on-containerized-locations" target="_blank" rel="noopener noreferrer">NAM monitors in containerized locations</A></P> <P><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp;<SPAN>&nbsp;</SPAN><A href="https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Troubleshooting-Map/ta-p/250426" target="_blank" rel="noopener">Synthetic troubleshooting map</A></P> <P><span class="lia-unicode-emoji" title=":open_book:">📖</span>&nbsp;&nbsp;<A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/Useful-Synthetic-ActiveGate-logs/ta-p/214478" target="_blank">Useful Synthetic ActiveGate logs</A>&nbsp;&nbsp;</P> Wed, 17 Jun 2026 12:58:55 GMT HannahM 2026-06-17T12:58:55Z https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-DNS-NAM-Monitors/ta-p/300483 <P><LI-TOC indent="15" liststyle="disc" maxheadinglevel="2"></LI-TOC></P> <DIV class="lia-message-template-content-zone"> <P>*<EM>Use a table of contents for longer articles.&nbsp;</EM></P> <H1>Summary</H1> <P><EM>*This is a mandatory section.</EM></P> <P><EM>Short description of which part of the Dynatrace platform the article refers to and what kind of problem it will help resolve / task it will describe.</EM></P> <P>&nbsp;</P> <H1>Problem</H1> <P><EM>*This is a mandatory section.</EM></P> <P><EM>Provide a precise description of the problem / task to be described.</EM></P> <P>&nbsp;</P> <H1>Troubleshooting steps</H1> <P><EM>*This section can be omitted.</EM></P> <P>&nbsp;</P> <H1>Resolution</H1> <P><EM>*This section can be omitted for ticket‑creation articles.</EM></P> <H1>What's next</H1> <P><EM>*This is a mandatory section.</EM></P> </DIV> Wed, 17 Jun 2026 12:58:55 GMT https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-DNS-NAM-Monitors/ta-p/300483 HannahM 2026-06-17T12:58:55Z https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-DNS-NAM-Monitors/tac-p/300683#M1135 <P>Thank you!&nbsp;<img class="lia-deferred-image lia-image-emoji" src="https://community.dynatrace.com/html/@9BD876A77FEF3D5EF4BC972CF8A97CB1/images/emoticons/take_my_money.png" alt=":take_my_money:" title=":take_my_money:" /></P> Fri, 12 Jun 2026 10:08:26 GMT https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-DNS-NAM-Monitors/tac-p/300683#M1135 AntonPineiro 2026-06-12T10:08:26Z https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-DNS-NAM-Monitors/tac-p/300705#M1136 <P>Thanks many</P> Sun, 14 Jun 2026 12:34:45 GMT https://community.dynatrace.com/t5/Troubleshooting/Private-Synthetic-Location-Not-Available-for-DNS-NAM-Monitors/tac-p/300705#M1136 Khejazi 2026-06-14T12:34:45Z