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

Release 0.15 #11

Merged
merged 2 commits into from
Apr 28, 2018
Merged

Release 0.15 #11

merged 2 commits into from
Apr 28, 2018

Conversation

cytopia
Copy link
Owner

@cytopia cytopia commented Apr 28, 2018

No description provided.

@cytopia cytopia self-assigned this Apr 28, 2018
@cytopia cytopia merged commit 5d29936 into master Apr 28, 2018
@cytopia cytopia deleted the release-0.15 branch April 28, 2018 14:30
@science695
Copy link

Great new features (will be using some of them shortly).

Have you thought about looking up the CNAMEs from the dns forwarding servers in the env file?

@cytopia
Copy link
Owner Author

cytopia commented Apr 30, 2018

Have you thought about looking up the CNAMEs from the dns forwarding servers in the env file?

What do you mean by that?

@science695
Copy link

science695 commented Apr 30, 2018

Say I have local DNS servers for internal.com

And I want to cname server.loc.internal.com to an internal DNS record: server.internal.com.

Google DNS doesn't know about: server.internal.com.

But I have set my internal dns servers in the BIND_DNS_RESOLVER env variable.

If you could query a dns server from that variable instead of google dns, it would be more likely to resolve internal hosts.

I can see how it could get more complicated because the RESOLVER field accepts multiple dns servers, but .... just a thought

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

Successfully merging this pull request may close these issues.

None yet

2 participants