Switch existing Account from powerdns to cloudflare - inconsistent behavior?

Bug reports
1
  • What version of apnscp are you running?
    cpcmd misc_cp_version
    revision: dc17cacc523c77f0ec582ddf21e3c292f0911e5c
    timestamp: 1745540622
    ver_maj: 3
    ver_min: 2
    ver_patch: 47
    ver_pre: ‘’
    dirty: false
    debug: false
  • Which version of RHEL or CentOS are you using?
    cat /etc/redhat-release
    AlmaLinux release 8.10
  • Can you reproduce this bug reliably? Provide steps. If not, provide steps to the best of your recollection.
    Yes.
  1. Have a site with powerdns dns provider enabled and rolled
  2. switch dns provider from powerdns to cloudflare and also fill dns key

Hello there,

unsure if this is a bug or wanted behavior. Maybe I missed something.

I have an existing account switched from powerdns provider to cloudflare including jumpstard which was more or less okay:

  • needed to add a lot of records manually which weren’t transfered with jumpstard (looks like sth like a ‘default’ template is created at cloudflare instead of all existing records at powerdns)
  • needed to modify all transfered TXT-Records where the content needs to be in quotation marks

After the change the cloudflare record management “inside” the account is fine but at Nexus level there’s still the powerdns-zone-management.

Would be great if there’s also the actual provider management at nexus level and also incredible helpful if it’s possible to directly migrate all existing records up to cloudflare.

Thank you for your time in advance!

Best regards