Skip to content

Commit f38164f

Browse files
authored
asz hci no such host 55000 error
1 parent 408e3ea commit f38164f

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -247,13 +247,21 @@ For general help resolving issues related to Azure Arc-enabled VMs on Azure Stac
247247

248248
### Action failed - no such host
249249

250-
When deploying Arc resource bridge, if you receive an error with `errorCode` as `PostOperationsError` and `errorResponse` as code `GuestInternetConnectivityError` and `no such host`, then the error may be caused by the appliance VM IPs not having reachability to the endpoint specified in the error.
250+
When deploying Arc resource bridge, if you receive an error with `errorCode` as `PostOperationsError`, `errorResponse` as code `GuestInternetConnectivityError` and `no such host`, then the error may be caused by the appliance VM IPs not having reachability to the endpoint specified in the error.
251251

252252
Error example:
253253

254254
`{ _errorCode_: _PostOperationsError_, _errorResponse_: _{\n\_message\_: \_{\\n  \\\_code\\\_: \\\_GuestInternetConnectivityError\\\_,\\n  \\\_message\\\_: \\\_Not able to connect to http://aszhcitest01.company.org:55000. Error returned: action failed after 5 attempts: Get \\\\\\\_http://aszhcitest01.company.org:55000\\\\\\\_: dial tcp: lookup aszhcitest01.company.org: on 127.0.0.53:53: no such host. Arc Resource Bridge network and internet connectivity validation failed: cloud-agent-connectivity-test. 1. Please check your networking setup and ensure the URLs mentioned in : https://aka.ms/AAla73m are reachable from the Appliance VM.   2. Check firewall/proxy settings`
255255

256-
In the example, the appliance VM IPs are not able to access `http://aszhcitest01.company.org:55000`. Please work with your network administrator to grant the proper access to the appliance VM IPs.
256+
In the example, the appliance VM IPs are not able to access `http://aszhcitest01.company.org:55000` which is the MOC endpoint. Please work with your network administrator to make sure that the DNS server is able to resolve the required urls.
257+
258+
To test connectivity to the DNS server:
259+
260+
```ping <dns-server.com>```
261+
262+
To check if the DNS server is able to resolve an address, from a machine where we can reach the DNS servers run:
263+
264+
```Resolve-DnsName -Name "http://aszhcitest01.company.org:55000" -Server "<dns-server.com>"```
257265

258266
### Authentication handshake failure
259267

0 commit comments

Comments
 (0)