<?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 vSatellite 'unable to remote...no such host' (Solution) in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/vsatellite-unable-to-remote-no-such-host-solution/m-p/1422667#M1014</link>
    <description>&lt;P&gt;I've installed a vSatellite on a Ubuntu VM in our GCP tenant to help managed cloud-based workloads.  As a standard practice, we build VMs with a traditional FQDN in Cloud DNS in a Shared VPC / Inter-connect topology.  When trying to create a new Machine type and using the remote machine's FQDN, Venafi returns:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;I&gt;"An error occurred while attempting to connect to the machine. The error message was 'unable to remote: unknown error Post "https://&amp;lt;FQDN&amp;gt;:5985/wsman": dial tcp: lookup &amp;lt;FQDN&amp;gt; on 10.43.0.10:53: no such host'"&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found this is due to the local K3s CoreDNS not having a resolver pointed to GCPs link-local metadata server IP (169.254.169.254).  Tried a couple of different solutions, but directly editing the CoreDNS config-map was lost each time the server was rebooted or the vSatellite was restarted.  The better solution was to add add the following configuration files to the /etc/rancher/k3s directory since these don't seem to be touched during restarts.&lt;/P&gt;&lt;CODE&gt;$ sudo tee -a /etc/rancher/k3s/resolv.conf &amp;lt;&amp;lt;EOF
nameserver 169.254.169.254
EOF&lt;/CODE&gt;&lt;CODE&gt;$ sudo tee -a /etc/rancher/k3s/config.yaml &amp;lt;&amp;lt;EOF
kubelet-arg:
  - "resolv-conf=/etc/rancher/k3s/resolv.conf"
EOF&lt;/CODE&gt;&lt;P&gt;Just wanted to share in case anybody else out there has run into something similar with their Cloud provider.&lt;/P&gt;</description>
    <pubDate>Mon, 18 May 2026 15:26:07 GMT</pubDate>
    <dc:creator>nkorosi</dc:creator>
    <dc:date>2026-05-18T15:26:07Z</dc:date>
    <item>
      <title>vSatellite 'unable to remote...no such host' (Solution)</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/vsatellite-unable-to-remote-no-such-host-solution/m-p/1422667#M1014</link>
      <description>&lt;P&gt;I've installed a vSatellite on a Ubuntu VM in our GCP tenant to help managed cloud-based workloads.  As a standard practice, we build VMs with a traditional FQDN in Cloud DNS in a Shared VPC / Inter-connect topology.  When trying to create a new Machine type and using the remote machine's FQDN, Venafi returns:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;I&gt;"An error occurred while attempting to connect to the machine. The error message was 'unable to remote: unknown error Post "https://&amp;lt;FQDN&amp;gt;:5985/wsman": dial tcp: lookup &amp;lt;FQDN&amp;gt; on 10.43.0.10:53: no such host'"&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found this is due to the local K3s CoreDNS not having a resolver pointed to GCPs link-local metadata server IP (169.254.169.254).  Tried a couple of different solutions, but directly editing the CoreDNS config-map was lost each time the server was rebooted or the vSatellite was restarted.  The better solution was to add add the following configuration files to the /etc/rancher/k3s directory since these don't seem to be touched during restarts.&lt;/P&gt;&lt;CODE&gt;$ sudo tee -a /etc/rancher/k3s/resolv.conf &amp;lt;&amp;lt;EOF
nameserver 169.254.169.254
EOF&lt;/CODE&gt;&lt;CODE&gt;$ sudo tee -a /etc/rancher/k3s/config.yaml &amp;lt;&amp;lt;EOF
kubelet-arg:
  - "resolv-conf=/etc/rancher/k3s/resolv.conf"
EOF&lt;/CODE&gt;&lt;P&gt;Just wanted to share in case anybody else out there has run into something similar with their Cloud provider.&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2026 15:26:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/vsatellite-unable-to-remote-no-such-host-solution/m-p/1422667#M1014</guid>
      <dc:creator>nkorosi</dc:creator>
      <dc:date>2026-05-18T15:26:07Z</dc:date>
    </item>
  </channel>
</rss>

