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

Add support for dnsmasq #89

Closed
thedebugger opened this issue Nov 13, 2014 · 5 comments
Closed

Add support for dnsmasq #89

thedebugger opened this issue Nov 13, 2014 · 5 comments

Comments

@thedebugger
Copy link
Contributor

What do you guys think about adding support for dnsmasq in separate recipe? I can submit a pull request.

@lyrixx
Copy link
Contributor

lyrixx commented Nov 14, 2014

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.

@thedebugger
Copy link
Contributor Author

@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.

@adrienbrault
Copy link

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

@johnbellone
Copy link
Contributor

I don't think this is an enhancement on our end. Its something you would provide in an environment or wrapper cookbook.

@lock
Copy link

lock bot commented Apr 25, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants