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.

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

Allow duplicate entries in Bind9 provider - dont alway's assume an update. #3

Open
lazypower opened this issue Jun 5, 2014 · 3 comments

Comments

@lazypower
Copy link
Owner

No description provided.

@mirw
Copy link
Contributor

mirw commented May 1, 2015

I'm using the DNS charm's programmable-multiple interface as part of the Clearwater Juju Charms (at https://github.com/Metaswitch/clearwater-juju/tree/dnsaas).

I'm hitting this issue because we add multiple A records for the same domain name to represent multiple servers in the same cluster. Unfortunately, each new A record overwrites the previous one, rather than adding to the list, so all load is sent to the last node that came up.

@lazypower
Copy link
Owner Author

I'll try to get some time allocated this week to get this update in place @mirw

Sorry you hit this - it was known behavior on initial publish. 🚒 time to fight fires it seems

@lazypower lazypower added this to the v0.1.1 milestone May 4, 2015
@mirw
Copy link
Contributor

mirw commented May 5, 2015

@chuckbutler, thanks for the update!

Tiers containing single hosts work fine - it's just when we scale up... but juju add-unit makes it very easy to do this, and it makes an impressive demo!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants