Thank you for the responses.
It turned out to be pilot error. I had a virtual machine that was
running dnsmasq on the same IP address that was not part of the cluster.
I had entered poweroff at the command line and then started bringing up
the new DNS server. It turns out that the old server
Or if there's a way to get your dnsmasq server to bind to a specific IP
address, that's an even better solution.
On 3/23/2012 8:27 PM, Trevor Hemsley wrote:
I'd guess that your replies are going back with the wrong source IP
address on them and the Windows clients are being picky about
In the dnsmasq.conf file I have
listen-address=127.0.0.1
listen-address=192.168.1.250
Where 192.168.1.250 is the virtual IP.
Otherwise, I think it will listen on all interfaces.
On 3/24/2012 7:22 PM, Alan Robertson wrote:
Or if there's a way to get your dnsmasq server to bind to a specific
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=192.168.1.250 cidr_netmask=24 \
op monitor
Did dnsmasq log that it is listening on the cluster address? You could try
adding an iptables nat rule to the box and see if that works. Nat the cluster
address for port 53 to the local server ip.
Sent from my iPad
On Mar 23, 2012, at 9:35 PM, Gregg Stock gr...@damagecontrolusa.com wrote:
I'd guess that your replies are going back with the wrong source IP
address on them and the Windows clients are being picky about accepting
them. Perhaps you need to investigate ocf:heartbeat:IPsrcaddr
On 24/03/12 01:35, Gregg Stock wrote:
I'm have some interesting behavior with a pacemaker
