On 1/24/2012 12:42 AM, Marc Haber wrote:
On Mon, Jan 23, 2012 at 05:42:16PM -0800, Rory Toma wrote:
I'm not sure that this is a powerdns problem, per se, but it seems
to only affect powerdns.
I have a keepalived setup using a /16 network. When pdns binds to
the keepalived port, udp queries work just fine, but tcp queries
fail with a "tcp port domain unreachable".
Can PowerDNS cope with an IP address being configured after PowerDNS
was started? What does netstat say wrt listening ports?
Yes, my keepalived and powerdns startup scripts add the IP address in
for listening. Both UDP and TCP port 53 show up in netstat.
I have an exact duplicate of this setup using /24's, and everything
works fine.
Which prompts the question, why are you using a /16? I have never seen
a LAN this large.
Because I inherited it, and undoing it is not feasible at the moment.
Is there some obscure setting I'm missing? I'm running pdns 2.9.22.5
(I can't upgrade to newer because I rely on a specific behavior in
this version)
Just out of curiosity: Which specific behavior?
I need it to forward queries, even queries where power dns is SOA, to
another name server.
Greetings
Marc
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
