[Pdns-users] pdns-recursor + heartbeat

[Matt Patterson]

All,

 

I have a small issue. I'm attempting to setup 2 pdns-recursor servers on
our network in a cluster using the heartbeat high availability foo.

 

Here's my problem.   In the configuration, it states that I need to set
local-addresses in order to get pdns-recursor up and running otherwise
it only listens on localhost.  In previous versions, it apparently bound
to any but was changed due to security issues with some admins having
open resolvers.  Here's where I start to run into an issue...Within my
cluster configuration, I'm doing an Active/Active setup so one server
takes one IP and the other gets a different IP. If one node in the
cluster fails, the IP moves over to the other server.  This causes a
problem for pdns-recursor as that new IP is not in the configuration so
even though it has successfully moved over to the other server, it is
not serving up DNS so to the end user, it is down.  Adding it to the
pdns configuration ahead of time causes an issue where the pdns-recursor
does not start as this is considered a mistake in the configuration.

 

Has anyone else run into an issue like this?  Is there a way to get
pdns-recursor to bind to any?

 

-Matt Patterson

mpatterson at lightedge.com

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20061220/ecd077a3/attachment.html>