Hi Pieter,
I can understand that the schema upgrade is needed for a new DNSSEC
feature: in our scenario DNSSES is unused, so I'm quite confident that your
suggestion will work.
Thanks a lot
On Tue, 17 Mar 2020 at 12:48, Pieter Lexis via Pdns-users <
pdns-users@mailman.powerdns.com> wrote:
> Hi
Hi Giovanni,
On 3/17/20 12:15 PM, Giovanni Vecchi via Pdns-users wrote:
> thanks for your quick reply.
> If 4.2 queries do not ask for that field, I can't figure out what could
> go wrong, isn't it?
> Otherwise, what's the best upgrade path for this scenario? May I need to
> stop every powerdns in
Hi Peter,
thanks for your quick reply.
If 4.2 queries do not ask for that field, I can't figure out what could go
wrong, isn't it?
Otherwise, what's the best upgrade path for this scenario? May I need to
stop every powerdns instance -> upgrade database schema -> upgrade every
powerdns instances ->
Hi Giovanni,
On 3/16/20 6:11 PM, Giovanni Vecchi via Pdns-users wrote:
> my scenario is the following:
> - several 4.2 Authoritative servers
> - multi-master database configuration (Percona XtraDB Cluster for
instance)
>
> In order to upgrade to 4.3 and avoid downtime, is it safe to upgrade the
>
Hi guys,
my scenario is the following:
- several 4.2 Authoritative servers
- multi-master database configuration (Percona XtraDB Cluster for instance)
In order to upgrade to 4.3 and avoid downtime, is it safe to upgrade the
database schema first and every server then?
Thanks a lot
__
