[Pacemaker] Dnsmasq

Gregg Stock gregg at damagecontrolusa.com
Fri Mar 23 21:35:11 EDT 2012

I'm have some "interesting" behavior with a pacemaker managed DNS 
server.  Here is the basic setup:

primitive p_dnsmasq lsb:dnsmasq \
         op monitor interval="60s" timeout="30s"
primitive p_ip_dnsmasq ocf:heartbeat:IPaddr2 \
         params ip="" cidr_netmask="24" \
         op monitor interval="10s"
order o_ip_before_dns inf: p_ip_dnsmasq p_dnsmasq

The cluster seems to manage the resource ok.

If the dnsmasq server is running on the hosts regular ip address, 
everything is fine. When switching to the cluster managed ip address, I 
get the following behavior on our network. The behavior was the same for 
various permutation of the listening addresses in the dnsmasq.conf file.

1. Linux hosts are fine.
2. Windows and Mac hosts can ping the DNS server but don't get DNS 
service. I was able to verify that the requests were getting to the DNS 
server but the replies were getting and ICMP destination unreachable on 
the way back.

I was able fine a tidbit of information here 

         A destination unreachable ICMP reply is normally generated by 
the kernel
         when there is nothing listening on that port. The most likely 
reason for
         that is that the dnsmasq process no longer exists. If that's 
the case
         the problem changes into "find why the dnsmasq daemon is exiting".

This doesn't seem to be completely applicable because the dnsmasq daemon 
is running.

Any additional information required?

Thanks in advance.

Best regards,
Gregg Stock

More information about the Pacemaker mailing list