Hi MRob,
Could you please try a ‘dig AXFR domain.com’ from your slave?
Could you also provide us a full packet capture (pcap if possible)? I am
starting to suspect a firewall issue…
Frank
> On 1 Dec 2018, at 22:44, MRob wrote:
>
>> All supermaster problems I know of can be resolved by chec
All supermaster problems I know of can be resolved by checking the
checklist:
https://doc.powerdns.com/authoritative/modes-of-operation.html?highlight=supermaster#supermaster-automatic-provisioning-of-slaves
* supermaster support must be enabled
I already asked about this on unanswered inquiry
On Sat, Dec 01, 2018 at 08:37:16PM +, MRob wrote:
> As I have had no luck to understand why supermaster only create entry in
> Received NOTIFY for example.com from 1.1.1.1:2101 for which we are not
> authoritative (Refused)
>
> Received unsuccessful notification report for 'example.com' from 2
As I have had no luck to understand why supermaster only create entry in
``domains'' table but not in ``records'' and AXFR never happen again
(https://mailman.powerdns.com/pipermail/pdns-users/2018-November/025624.html)
I think maybe it's a bug in pdns 4.1 so I install 4.2 on slave (master
stil
