On Wed, Sep 08, 2010 at 08:31:45PM +0300, George wrote:
I have CentOS 5.5 and powerdns 2.9.21 set up as a slave server. My
problem is that pdns does not reply to queries that come from outside
on any secondary IP . Here's the full story:
Can you run:
grep local-address /etc/powerdns/pdns.conf
On Wed, Sep 08, 2010 at 08:44:01PM +0300, George wrote:
Here are the outputs:
[r...@webprod02 ~]# grep local-address /etc/pdns/pdns.conf
# local-address Local IP addresses to which we bind
local-address=0.0.0.0
(...)
pdns[6269]: It is advised to bind to explicit addresses with the
Thanks!
I changed local-address and included all the IPs with a , between them
and it worked.
I thought 0.0.0.0 is supposed to make it work on all IPs.
On Wed, Sep 8, 2010 at 8:46 PM, bert hubert bert.hub...@netherlabs.nl wrote:
On Wed, Sep 08, 2010 at 08:44:01PM +0300, George wrote:
Here are
On Sun, Aug 29, 2010 at 09:17:01PM +, Brad Dameron wrote:
The release process for 3.3 can now start - only 1 feature request left
to
finish.
Good to hear Bert. I'll run it through the ringer on Monday and see if we can
reproduce the problem. Cross fingers that it is fixed.
Brad,
In my pdns/ldap
(tree) on CentOS 5.5, I am setting up a domain (say:
'example.com') with its single SOA record. This has several
virtual subzones (a.example.com, b.example.com etc.) which
include their own MX records but are not delegated: the same NS
Indeed, I have confirmed that pdns does not send a complete set of
records during AXFR, by executing:
# dig example.com AXFR @dns.example.com
where dns.example.com is the pdns/ldap server. The output is exactly the
content of slave files.
So, why aren't all zone records included in the
On Thu, Sep 09, 2010 at 12:10:53AM +0300, Nikolaos Milas wrote:
Indeed, I have confirmed that pdns does not send a complete set of
records during AXFR, by executing:
# dig example.com AXFR @dns.example.com
where dns.example.com is the pdns/ldap server. The output is exactly
the
