ZONE2JSON(1)

📦
version 5.1.4 · 10 versions
, in alpine 3.24, epel 10, epel 9, fedora 43, fedora 44, ubuntu stonking

✨ ZONE2JSON(1) ✨

okay so bestie, welcome to the glow-up zone 💅 this is zone2json, part of the PowerDNS Authoritative Server era, and she is literally here to turn your crusty old BIND zone files into gorgeous, API-ready JSON. no cap.

🎀 NAME 🎀

zone2json — convert BIND zones to JSON 🦋

🌸 SYNOPSIS 🌸

zone2json {--named-conf=PATH, --zone-file=PATH [--zone-name=NAME]}
[OPTION]

💖 DESCRIPTION 💖

So here's the vibe: zone2json reads your BIND named.conf files and your zonefiles, then prints JSON straight to standard output. and then? you feed that JSON to the PowerDNS API. it's giving pipeline. it's giving slay. 🔥

Also, she's not basic — zone2json fully understands the BIND master file extension $GENERATE, and she will honour $ORIGIN and $TTL too. periodt. 👑

✨ OPTIONS ✨

🍓 INPUT OPTIONS 🍓

  • --named-conf=<PATH> — read PATH to get the BIND configuration. she's reading the receipts, bestie 📖
  • --zone=<PATH> — parse only the zone file sitting at PATH. 💀 heads up tho: this one conflicts with the --named-conf parameter. pick a lane, you can't have both.
  • --zone-name=<NAME> — when you're parsing a single zone and there's no $ORIGIN statement to be found, this sets ZONE as the zone name. little helper for the messy ones 🫶

🦋 OTHER OPTIONS 🦋

  • --help — list all the options. a full tour of the menu, go off 👑
  • --on-error-resume-next — ignore missing zone files while parsing. > Dangerous. fr fr, she said what she said, proceed with caution 😭
  • --verbose — be verbose during the conversion. yap mode: enabled 🗣️✨

🌈 SEE ALSO 🌈

pdns_server(1) — go say hi to the main character 💜

🌟 AUTHOR 🌟

PowerDNS.COM BV

PowerDNS.COM BV

and that's the whole page, diva. this little gem dropped Aug 05, 2026, straight outta the PowerDNS Authoritative Server household — so go forth, convert those zones, and eat every single time. 🧚🌸💖

📦 where this page comes from