-
Notifications
You must be signed in to change notification settings - Fork 92
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
adding additional CNAME records #8
Comments
You can add aliases or arbitrary responses with the HTTP server but A records are only supported. I'm ok to adding CNAME if you are willing to maintain it. But maybe then it would make sense to make a separate project that has the DNS/HTTP server logic and is included as a package by |
Just spotted a fork of this project that seems to have some alias functionality. https://github.com/t0mk/dnscock |
thx for your quick response. Actually CNAME is not my main concern, so additional A-records are probably fine as well. The most important is probably the ease of maintenance vi ENV varibles like DNSDOCK_ALIAS or similar. This seems to be a good a idea. |
Since #16 has been merged, this issue can be closed :) |
First of all thx for providing dnsdock, it's a nice tool to add simple dns/service discovery inside docker.
For my use case I would like to add multiple hostname/aliases to a single running container. For this reason I'd like to be able to add "arbitrary" CNAME records into dns.
Does this sound like a valid use case for dnsdock?
Is this something that is supported by dnsdock already or something you could imagine to add?
The text was updated successfully, but these errors were encountered: