Why does the location subdomain not route traffic to control plane hosts?

After you assign hosts to your Satellite location control plane, you see a message similar to the following.

R0036 The location subdomains are not correctly routing traffic to your control plane hosts. Verify that the location subdomains are registered with the correct IP addresses for your control plane hosts with the 'ibmcloud sat location dns' commands.

The Satellite location control plane is inaccessible through the location subdomains due to one of the following reasons:

The hosts are behind a firewall that blocks traffic within the location.
The DNS resolver for one or more hosts is not properly resolving the registered DNS endpoints.

Follow these steps to resolve your issue

Review the location subdomains and check the Records for the IP addresses of the hosts that are registered in the DNS for the subdomain.
```
ibmcloud sat location dns ls --location <location_name_or_ID>
```
For every host in your location, complete the following steps to log in to the host and check the DNS resolution.
1. Log in to the host machine.
  - If the host is not assigned to the Satellite location control plane or a cluster, you can SSH into the host machine.
  - If the host is assigned to the Satellite location control plane or a cluster:
    1. Remove the host from your Satellite location.
    2. Reload the operating system of the host or reboot the instance.
    3. Attach the host back to your Satellite location, but do not assign it. Later, after you complete these troubleshooting steps, you can re-assign the host back to your Satellite location control plane or cluster.
    4. SSH into the host machine.
2. Look up each location subdomain that you found in step 1. Check whether the IP address that resolves matches the host IP addresses that you found in step 1. If the host's DNS resolver does not resolve the subdomains to the expected IP addresses, ensure that your hosts have the required minimum outbound connectivity.
```
nslookup <subdomain>
```
3. Use netcat on each location subdomain on port 30000 to test host connectivity. If any subdomain's netcat operation times out, ensure that your hosts meet the host network requirements.
```
nc -zv <subdomain> 30000
```
  Successful output:
```
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connection refused.
```
If are still unable to resolve the issue, open a support case. In the support case description, include all debugging steps that you followed and the output from these steps.