-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Custom DNS records in addition to wildcard #6
Conversation
Allows an Environment variable to add additional dns entries (before the wildcard address). Allows greater flexibility for the bind dns server while allowing the simple configuration continue working.
Including documentation and example usage for adding in extra dns records via the CUSTOM_DNS env variable
To make use of this new feature in the bind container (cytopia/docker-bind#6), this documents how to setup the CUSTOM_DNS environment variable.
Mentioning the new feature for custom dns in the bind container (cytopia/docker-bind#6)
Mentioning the new feature for custom dns in the bind container (cytopia/docker-bind#6)
@science695 very good idea. I am currently looking into and thinking my head around it. So far I think this solves a few issues and I will merge it. One thing however I might change is the custom DNS to not use the currently chosen wildcard TLD, but rather be able to use any domain. I think that will give you more power/control overall. So I will rewrite it afterwards to be able to specify the following:
This will mean that
Being able to also map DNS names into your chosen DNS name will also allow you to make use of host.docker.internal DNS name, which always points to the IP address of your host computer from within a container. Update: This will also solve the problem accessing the host computer as described here: https://deliciousbrains.com/devilbox-local-wordpress-development-docker/#communicating-with-external-hosts Thoughts on that? |
Does that mean you would add the ability to do cnames and other tags (instead of just A records)? Something like:
I'm not sure what docker does with ipv6, but that ^ functionality could open up ipv6. (The code in this request is only the ipv4 "A" record) |
Similar, you only need two values:
If the running container is able to resolve For extra hosts I will also make sure to add reverse DNS. |
@science695 I will close your PR in favour of a major rewrite: #8 Thanks a lot for this idea and your effort, unfortunately I could not merge yours, because of basically changing everything. |
I'm using this bind container with devilbox, but I'm needing to run both apache/php-fpm, and another container running a ngingx (api-umbrella).
This feature would allow you to pass in an environment variable and specify other subdomains (under the $WILDCARD_DOMAIN) that go to different ip addresses (or even sub-subdomain wildcards: *.a.loc)
While being globally available, it should also work with devilbox.