Internal DNS Resolver for totem

[sukrit007]

Background While replacing our current totem cluster with new totem cluster , it became difficult to validate applications that depend upon each other. Currently these applications are wired using route 53 DNS names , however since we did not roll over to new cluster, it started resolving to old cluster.

What is needed ? We need some mechanism to easily resolve services running on same cluster.

Minimal Requirements

• Additional alias that resolves to current cluster. (e.g. .cluster)
• Any services that uses pattern service-name.cluster should always resolve to the current cluster when looked up from current cluster.
• Cluster addresses should automatically be created for every deployment (no additional config needed)

[sukrit007]

@mmoulton @kennedyj @ctrimble @jacobheun @dtackett @abathingchris , Comments / Suggestions: Feel free to chime in. Also let us know how useful this would be to you to decide priority. (p1, p2, p3, p4)