-
-
Notifications
You must be signed in to change notification settings - Fork 244
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
Add support for dnsmasq #89
Comments
I'm not sure to understand correctly the link between dnsmasq and consul? Do you want to leverage consul service discovery to configure dnsmasq? If so, it looks like there is better way to handle that. So I would not tied this cookbook to dnsmasq. |
@lyrixx I meant for DNS forwarding – http://www.consul.io/docs/guides/forwarding.html – but dnsmasq instead of bind. We run dnsmasq on all Consul client nodes insteading of serving Consul queries from our centeral dns server. |
http://www.morethanseven.net/2014/04/25/consul/ Yes, this would be nice, and simple What I've done that works on amazon linux: package 'dnsmasq' do
action :install
end
service 'dnsmasq' do
action :start
end
file '/etc/dnsmasq.conf' do
content "server=/consul/127.0.0.1##{node[:consul][:ports][:dns]}"
notifies :reload, "service[dnsmasq]", :immediately
end
service "network" do
action :nothing
end
file "/etc/dhcp/dhclient.conf" do
content <<-eos
timeout 300;
prepend domain-name-servers 127.0.0.1;
eos
notifies :restart, "service[network]"
end |
I don't think this is an enhancement on our end. Its something you would provide in an environment or wrapper cookbook. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What do you guys think about adding support for dnsmasq in separate recipe? I can submit a pull request.
The text was updated successfully, but these errors were encountered: