Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DNS should not share -client-addr parameter #253

Closed
jefferai opened this issue Jul 21, 2014 · 1 comment
Closed

DNS should not share -client-addr parameter #253

jefferai opened this issue Jul 21, 2014 · 1 comment

Comments

@jefferai
Copy link
Member

Unlike RPC and HTTP, Consul data cannot be changed via DNS. As a result, a simple way to use Consul in a semi-secure fashion would be to expose the DNS interface without exposing the HTTP/RPC interfaces. Sadly, these three are lumped together in the same bind flag. Separating out DNS would be useful.
armon added a commit that referenced this issue Sep 2, 2014
@armon
agent: Address overrides. Fixes #301 and #253
e86c5b2
@armon
Copy link
Member

armon commented Sep 2, 2014

Fixed by e86c5b2

@armon armon closed this as completed Sep 2, 2014
duckhan pushed a commit to duckhan/consul that referenced this issue Oct 24, 2021
@lkysow
Merge pull request hashicorp#253 from hashicorp/generate-fed-secret
993ecf8 
Add create-federation-secret command
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jefferai @armon