Re: [ClusterLabs] PCS, Corosync, Pacemaker, and Bind (Ken Gaillot)

2016-03-19 Thread Andrei Borzenkov
On Wed, Mar 16, 2016 at 9:35 PM, Mike Bernhardt wrote: > I guess I have to say "never mind!" I don't know what the problem was > yesterday, but it loads just fine today, even when the named config and the > virtual ip don't match! But for your edamacation, ifconfig does NOT

Re: [ClusterLabs] PCS, Corosync, Pacemaker, and Bind (Ken Gaillot)

2016-03-19 Thread Dennis Jacobfeuerborn
On 17.03.2016 08:45, Andrei Borzenkov wrote: > On Wed, Mar 16, 2016 at 9:35 PM, Mike Bernhardt wrote: >> I guess I have to say "never mind!" I don't know what the problem was >> yesterday, but it loads just fine today, even when the named config and the >> virtual ip don't

Re: [ClusterLabs] PCS, Corosync, Pacemaker, and Bind

2016-03-19 Thread Ken Gaillot
On 03/15/2016 06:47 PM, Mike Bernhardt wrote: > Not sure if this is a BIND question or a PCS/Corosync question, but > hopefully someone has done this before: > > > > I'm setting up a new CentOS 7 DNS server cluster to replace our very old > CentOS 4 cluster. The old one uses heartbeat which is

Re: [ClusterLabs] PCS, Corosync, Pacemaker, and Bind (Ken Gaillot)

2016-03-18 Thread Mike Bernhardt
I guess I have to say "never mind!" I don't know what the problem was yesterday, but it loads just fine today, even when the named config and the virtual ip don't match! But for your edamacation, ifconfig does NOT show the address although ip addr does: ip addr 1: lo: mtu