Awesome, thank you.
Sent from my iPhone
> On Apr 25, 2025, at 12:57 AM, Miod Vallat wrote:
>
>
>>
>> so i suppose i can stick with mysql group-replication and it is in fact ok
>> to use then?
> I suppose so - I see nothing which would prevent this from working now,
> the foreign key constra
so i suppose i can stick with mysql group-replication and it is in fact
ok to use then?
I suppose so - I see nothing which would prevent this from working now,
the foreign key constraints are only an optimization. But be sure to let
us know if you encounter any problem with this setup!
I will
On 4/24/25 11:50 AM, Miod Vallat wrote:
You might want to drop your PowerDNS database and create it again from
the SQL schema, without applying the "enable foreign keys" script.
HTH,
Miod
that worked like a charm. i was now able to use pdnsutil load-zone
without issue:
root@ns1:~# pdnsuti
hello,
On 4/24/25 2:57 AM, Miod Vallat via Pdns-users wrote:
You are not using zone2sql correctly
ahh, understood. i re-read the docs and yep, i see that now. misread it.
thank you. i'll come back to this if needed later. unless this turns out
to be the only way possible somehow.
--
Thank
there is an error:
2025-04-24T15:27:41.272419Z 1861 [ERROR] [MY-011543] [Repl] Plugin
group_replication reported: 'Table records has a foreign key with
'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible
with Group Replication.'
Ah, you probably enabled foreign keys, a
On 4/24/25 1:52 AM, Miod Vallat via Pdns-users wrote:
There should be a more detailed error in the group replication plugin
logs, can you check what error gets reported there?
there is an error:
2025-04-24T15:27:41.272419Z 1861 [ERROR] [MY-011543] [Repl] Plugin
group_replication reported: 'Ta
On 4/24/25 10:51 AM, Chris Wopat wrote:
Also, instead of zone2sql, consider setting the new servers up from
scratch as secondaries to your current production. And set it to AXFR
all zones over. We ran into many issues with zone2sql and this worked
better for us.
Not remembering specifics but
Also, instead of zone2sql, consider setting the new servers up from scratch
as secondaries to your current production. And set it to AXFR all zones
over. We ran into many issues with zone2sql and this worked better for us.
Not remembering specifics but it was the sanitization of the records as
the
