Dnsmasq does not work if consul_client_address used about ansible-consul

[trumant]

@williamoneill - Nice catch! I'll have a fix PRed in a bit.

[MrMMorris]

@williamoneill what were you setting client_addr to that made dnsmasq not work? I have noticed that when I set it to 0.0.0.0 and dnsmasq is also set to that, dns lookups are broken until I set dnsmasq to 127.0.0.1

[MrMMorris]

After some testing, I can't even get my consul to work without setting client_addr to 0.0.0.0 and dns doesn't work in that instance unless the dnsmasq ip is 127.0.0.1.

@williamoneill not sure what your setup is like, but it seems that we should check if client_addr is 0.0.0.0 and if so, keep the dnsmasq ip as 127.0.0.1.

I also have a dns test, but I'm not sure if it would apply to all cases:

- name: check dns
  command: dig {{ consul_node_name }}.node.consul
  register: dns_test
  notify:
    - test dns

- name: test dns
  fail: msg="Consul DNS not resolving properly"
  when: "'{{ ansible_eth0.ipv4.address }}' not in dns_test.stdout"