Question: DNS name for a virtual-router with single route

[rkbalgi]

If you have a single route in the virtual-router, should its DNS name match the DNS name of the virtual service?

For example,
In https://github.com/aws/aws-app-mesh-examples/blob/master/examples/apps/colorapp/servicemesh/appmesh-colorapp.yaml

For all colours,

ColorTellerBlackVirtualNode:ServiceDiscovery:DNS.Hostname: = !Sub "colorteller-black.${ServicesDomain}"
ColorTellerBlueVirtualNode:ServiceDiscovery:DNS.Hostname: = !Sub "colorteller-blue.${ServicesDomain}"
ColorTellerRedVirtualNode:ServiceDiscovery:DNSHostname: = !Sub "colorteller-red.${ServicesDomain}"

but white,
ColorTellerWhiteVirtualNode:ServiceDiscovery:DNSHostname: = !Sub "colorteller.${ServicesDomain}"
(No -white??)

Can someone explain?

[rkbalgi]

Some more context to the above question -
I've setup an app mesh is setup similar to the colorteller (all artifacts created manually on the web console without cloud-formation) . All the services run on ECS fargate. There is a gateway service that calls a greeting service. The client makes a call to gateway service - curl http://gateway.local:8080/greeting/hello and the gateway application makes a call to the greeting service using a this URL - http://greeting.local:8080/greeting/hello_impl

(The application is written in Java)

greeting.local is the virtual service and there is a single node with DNS as greeting_1.local with 100% weight.

When I call gateway service which indirectly calls the greeting service, I get a UnknownHostException for greeting.local. What I assume should happen is for envoy to intercept the call and replace greeting.local with greeting_1.local?

The config_dump and other details are here - https://docs.google.com/document/d/1MxvKtMaXlO_06jb9OhaUyA8mYZ9pSwz256CWPneawvg/edit?usp=sharing

[rkbalgi]

The issue faced is described aws/aws-app-mesh-roadmap#65 and
aws/aws-app-mesh-roadmap#71. Closing this issue.