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

No way to denote when remote units should add host as DNS service #17

Open
lazypower opened this issue Jun 16, 2015 · 0 comments
Open

No way to denote when remote units should add host as DNS service #17

lazypower opened this issue Jun 16, 2015 · 0 comments
Assignees
@lazypower
Labels
bug charm
Milestone
v0.3.0

Comments

@lazypower
Copy link
Owner

In the current model, it is always assumed the DNS charm is providing the DNS. as of the crumbs of the rt53 branch are landing, this is not always the case, and we need a further qualifier to denote when the remote unit should add the host as a DNS server.
@lazypower lazypower self-assigned this Jun 16, 2015
@lazypower lazypower added this to the v0.3.0 milestone Jun 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lazypower lazypower

Labels
bug charm
Projects
None yet
Milestone
v0.3.0
Development

No branches or pull requests
1 participant
@lazypower