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

Make "listen-on-v6" a configurable option #134

Merged
merged 1 commit into from
Aug 5, 2015
Merged

Make "listen-on-v6" a configurable option #134

merged 1 commit into from
Aug 5, 2015

Conversation

djmofcourse
Copy link

Previously, the "listen-on-v6" option was hard-coded to the value "any" which limited IPv6 configurability.

This commit adds dns::server::options::listen_on_ipv6, allowing an array of values to be provided for the config option.

Previously, the "listen-on-v6" option was hard-coded to the value "any"
which limited IPv6 configurability.

This commit adds dns::server::options::listen_on_ipv6, allowing an array
of values to be provided for the config option.
@djmofcourse
Copy link
Author

Hi. Here's the output of a successful bundle exec rake beaker run: https://gist.github.com/djm256/606dda198806d6a91378

it { should contain_file('/etc/bind/named.conf.options').with_content(/2001:db8:2::\/124;$/) }
end

context 'when passing a string to listen_on_ipv6' do
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think you realy have to double check the validate_array function, it will be fine

solarkennedy added a commit that referenced this pull request Aug 5, 2015
Make "listen-on-v6" a configurable option
@solarkennedy solarkennedy merged commit 8b94af0 into ajjahn:master Aug 5, 2015
@solarkennedy
Copy link
Collaborator

Thanks!

@djmofcourse
Copy link
Author

Glad I could contribute. Thanks for a great module 👍

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.

2 participants