Powerdns behind load balancer thinking it's not authoritative

G

giggity

Guest
Hello,
We have 2 nameservers:
ns1.domain.com
ns2.domain.com

ns1 = dell r200 (let's call this ip: 192.168.0.2)
ns2 = coyote point load balancer which points to two OLD "joe's brand" servers running old versions of debian/pdns (let's call this ip: 192.168.0.3)
(the two old ones that are working fine are 192.168.0.11 and 192.168.0.12)

The plan is:
- Replace the ns1 r200 with a r410 (up and running/testing currently)
- Replace the tired pair of servers behind the load balancer with two VMs

I have everything installed and slowly testing things. The new nameservers respond when queried directly.

I'm running powerdns on all three. ns1-test is the master and the two VMs are slaves - running mysql replication off ns1.
I'm using another server we have as a recursor.

To test things, I placed one of the VMs behind the load balancer to see how things would fly..

First, I was getting responses like:
reply from unexpected source: 192.168.0.5#53, expected 192.168.0.3#53

I fixed that by adding a route for 192.168.0.5 to go out through the load balancer @ 192.168.0.3

Now, i'm down to my last issue to fix which is non-authoritative errors..
Dec 14 09:18:07 iqb2 pdns[7375]: Not authoritative for 'domain1.com', sending servfail to 123.123.123.123
Dec 14 09:18:22 iqb2 pdns[7375]: Not authoritative for 'domain2.com', sending servfail to 234.234.234.234
Dec 14 09:18:22 iqb2 pdns[7375]: Not authoritative for 'www.domain3.com', sending servfail to 133.133.133.133
Dec 14 09:18:37 iqb2 pdns[7375]: Not authoritative for 'www.domain4.org', sending servfail to 34.34.34.34
(these domains are all set up with my nameservers as primary and secondary)

When I query the load balancer (ns2 ip address), i'll sometimes get a good answer back.. and sometimes it'll say "connection timed out; no servers could be reached".

How do I tell pdns that it's authoritative for the domains?

Thanks
 


Hi,

PDNS is authoritative as long as it can find SOA records in your configured backend. Are you sure you have your backend configured and filled correctly?

- Peter (PowerDNS developer)
 
Sorry, yes - I figured this out..

Turns out it was running fine and it was telling the truth ;) We have a couple thousand zones and I thought the ones that it was complaining about were still active.

Thanks for such a great product!
 


Latest posts

Top