masters {
192.168.0.5 port 5300;
};
caused the auth server to fail to restart, but changing that to ;
masters {
192.168.0.5:5300;
};
got things moving ;
Aug 20 15:06:33 slave01 pdns_server[529]: Aug 20 15:06:33 Initiating
transfer of 'test.domain.com' from remote '192.168.0.5:5300'
Aug 20
On 2018-08-20 8:03 AM, Brian Candler wrote:
On 20/08/2018 15:00, Steve Rose wrote:
masters {
192.168.0.5;
};
"masters" has to point to the authoritative server. Try:
masters {
192.168.0.5 port 5300;
};
Possibly relevant: https://github.com/PowerDNS/pdns/issues/6240
On 20/08/2018 15:00, Steve Rose wrote:
masters {
192.168.0.5;
};
"masters" has to point to the authoritative server. Try:
masters {
192.168.0.5 port 5300;
};
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.
I am running a simple pdns and pdns-recursor 4.1.3 with auth server running
on port 5300 and the recursor on port 53 as per scenario 1 at
https://doc.powerdns.com/authoritative/guides/recursion.html, with one
master and one slave node in the cluster (both CentOS 7.3)
My slave is not receiving any
Background: We're using the "forward-zones-file" functionality of
PowerDNS recursor to forward some queries to a BIND server.
I see the following behavior for PowerDNS recursor 4.1.3 running on
a FreeBSD 11.2-STABLE server:
- Zone added to the list in forward-zones-file: The forwarding takes
effe
Hello Ed,
On 17 Aug 2018, at 15:36, Ed Santora wrote:
Is there some Lua script that can update the Recursors' forwarded
zones
list, via the API, when new local domains are added? Or, is there some
other method recommended that I missed? Google has been unusually
unhelpful.
The best suggesti
