-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for DNS discovery #185
Comments
I'd love to see this merged in. At the moment we have a mix of on-prem windows and aws windows+linux consul agents that want to discover the address of consul servers in aws that are part of an auto-scaling group. For the on-prem instances, it is really hard for them to find the addresses without hard-coding them into each agent config/more complicated certificates etc which we would like to avoid. It would be ideal if they could resolve a CNAME that contains multiple A records to the individual elements and use that. Will this PR ever get merged in? |
That's why I built this for non-cloud environments basically. In an on-preom environment you're basically limited to either standing up something to do this for you (e.g: Consul) or using regular DNS (which is pretty common). |
This could also be used in a Kubernetes cluster to resolve the DNS name of a headless service. |
Hi all 👋
Whilst there is the
mDNS
provider, but there isn't currently a plain DNS provider. This is primarily useful (at least for me) in a Docker Swarm cluster (yes these are still in use!)Is there any interest in this from the community?
The text was updated successfully, but these errors were encountered: