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 it was the sanitization of the records as they came over as we had a bunch of really old records in zones (from the 90s).In brief the method we used was:* Create all zones as secondaries in pdns, with your bind as primary: pdnsutil create-secondary-zone <zone> <bind IP>* convert to native when ready: pdnsutil set-kind <zone> native You could also do this in SQL. Don't blindly run these.* INSERT INTO domains (name,type,master) VALUES ('<zone>', 'SLAVE', '<bind IP>');* pdns_control rediscover * UPDATE domains SET type='NATIVE' WHERE type='SLAVE' ; --Chris
i would prefer to be able to do that, but this zone is currently hosted on squarespace (migrated from the defunct google domains). i'm not sure how i can allow the AXFR to my own NS. so what i did instead was to turn all of my dns records into a zone file i intended to import into my own NS (since squarespace also does not offer a zone file download feature).
if i'm wrong and the AXFR should be possible, please do advise! -- Thank you. Fabian S. OpenPGP: 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F
OpenPGP_0x5E3DAA18A1C22D8F.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
