Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

[dns] idiomatic support for containers with more than one name #364

Closed
rade opened this issue Jan 26, 2015 · 4 comments
Closed

[dns] idiomatic support for containers with more than one name #364

rade opened this issue Jan 26, 2015 · 4 comments

Comments

@rade
Copy link
Member

rade commented Jan 26, 2015

With weavedns one can create multiple DNS records for containers - with PUTs on the weavedns HTTP API. There are a few problems with that...

  1. Adding the records requires peeking under the hood of weavedns, i.e. there is no corresponding weave or docker command.
  2. The extra records do not survive a weavedns restart, since, unlike the hostname, the information is not part of the container's metadata and weavedns does not itself persist any data.
  3. weavdns only deals in A records; whereas for some use cases CNAMEs would be more appropriate.

Related to #226.

@inercia
Copy link
Contributor

inercia commented Mar 4, 2015

Any suggestion on how to solve the second issue? Do you suggest to add some persistence mechanism to WeaveDNS?

@rade
Copy link
Member Author

rade commented Mar 4, 2015

Do you suggest to add some persistence mechanism to WeaveDNS?

No! moby/moby#9013 would offer a solution.

@inercia
Copy link
Contributor

inercia commented Mar 4, 2015

I presumed you were not suggesting that... :)

So I guess this issue is blocked until moby/moby#9013 is solved...

@rade
Copy link
Member Author

rade commented May 7, 2015

I've captured points 2 and 3 in #635 and #636, respectively.

@rade rade added this to the 0.11.0 milestone Jan 15, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants