Internal DNS entries for instance tags
When a tag is applied to an instance it should generate an internal dns entry.
tag prod-db is applied to prod-db-1 instance which has an internal ip of 10.0.0.1
prod-db-1 would have a fqdn of: prod-db-1.c.project-1.internal and a lookup against that host from a different instance would resolve the ip to 10.0.0.1.
I'm proposing that additional host entries be added for tags. Example:
This is useful because just like tags are used for source/destination tags in the firewall they would also be useful via dns from the instances.
Yes, it's entirely possible to write scripts that determine these things by querying the API but it would also provide a wonderful convenience.
Thanks, we’re looking at this.
Matthew Lenz commented
Paul, wouldn't need to be unique. You can return multiple IPs for the same host.
I'm not sure this would work as you've described it, as a tag is not unique to a single instance. For example, you could label a handful of instances "staging". In that case, there couldn't be a DNS resource that uniquely identifies any single instance. Note, also, non-DNS entities like disks can be tagged.
While this may not be feasible, we are exploring making the instance name itself an automatic DNS entry.