From: Pdns-users on behalf of Fabian
A. Santiago
>On May 4, 2017 6:15:35 AM EDT, Remi Gacogne wrote:
>>On 05/04/2017 12:09 PM, Fabian A. Santiago wrote:
'allow-notify-from' defaults to '0.0.0.0/0,::/0', which allows
everything. Of course additional checks are performed afterward
On May 4, 2017 6:15:35 AM EDT, Remi Gacogne wrote:
>On 05/04/2017 12:09 PM, Fabian A. Santiago wrote:
>>> 'allow-notify-from' defaults to '0.0.0.0/0,::/0', which allows
>>> everything. Of course additional checks are performed afterwards,
>>> like checking if the configuration requires a valid TS
On 05/04/2017 12:09 PM, Fabian A. Santiago wrote:
>> 'allow-notify-from' defaults to '0.0.0.0/0,::/0', which allows
>> everything. Of course additional checks are performed afterwards,
>> like checking if the configuration requires a valid TSIG signature,
>> whether we are authoritative for the do
On May 4, 2017 3:52:40 AM EDT, Remi Gacogne wrote:
>On 05/04/2017 12:10 AM, David Jones wrote:
>> I have a PowerDNS server setup as a slave and see this in my logs
>> constantly:
>>
>> Received NOTIFY for example.com from 1.2.3.4 but remote is not
>> permitted by TSIG or allow-notify-from
>>
>>
On 05/04/2017 12:10 AM, David Jones wrote:
> I have a PowerDNS server setup as a slave and see this in my logs
> constantly:
>
> Received NOTIFY for example.com from 1.2.3.4 but remote is not
> permitted by TSIG or allow-notify-from
>
> I was hoping to not have to maintain a long list of master I
I have a PowerDNS server setup as a slave and see this in my logs constantly:
Received NOTIFY for example.com from 1.2.3.4 but remote is not permitted by
TSIG or allow-notify-from
I was hoping to not have to maintain a long list of master IPs in the
allow-notify-from. One would think that the
