Using an internal, container-to-container, route results in `Could not resolve host: my-route.apps.internal`

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Applications can talk directly to each other without sending traffic through Gorouter by using an internal route which will send traffic over the container-to-container network. This KB covers the case where using an internal route results in the message like:

Could not resolve host: my-route.apps.internal

or

request failed: Get http://backend.apps.internal:7007: dial tcp: lookup backend.apps.internal on 169.254.0.2:53: no such host 

Resolution

This happens when the route in question is not mapped to your application. Internal application routes will only resolve when they are actually mapped to your application. That is why you see "no such host" when the route is unmapped.

If you are seeing this error, please double check that the internal route is mapped to the application that needs to use it.