brew / Rang 4014

pdns mit Homebrew, apk, dnf, Nix, zypper, apt, pacman installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für pdns in AI-Agent-Workflows.

Installationsbefehl Sicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install pdns

local Homebrew formula metadata

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add pdns

Alpine Linux edge package indexes · pdns · Quelle: dl-cdn.alpinelinux.org

Fedora dnfverifiziert · 92%

sudo dnf install pdns

Fedora Rawhide package metadata · pdns · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%

nix profile install nixpkgs#pdns

nixpkgs package indexes · pkgs/by-name/pd/pdns/package.nix · Quelle: api.github.com

openSUSE zypperverifiziert · 92%

sudo zypper install pdns

openSUSE Tumbleweed package metadata · pdns · Quelle: download.opensuse.org

Debian aptverifiziert · 92%

sudo apt install pdns-backend-bind

Debian stable package indexes · pdns-backend-bind · Quelle: deb.debian.org

Arch Linux pacmanverifiziert · 92%

sudo pacman -S powerdns

Arch Linux sync databases · powerdns · Quelle: geo.mirror.pkgbuild.com

Überblick

Paketzusammenfassung

Authoritative nameserver

Projektlinks

Befehle und Aliase

pdns_control
pdns_server
pdnsutil
zone2json
zone2sql

Verlauf

Projektgeschichte und Nutzung

PowerDNS Authoritative Server is an open-source authoritative DNS server known for flexible storage backends, DNSSEC support, and tooling for operating hosted DNS zones.

Projektgeschichte

PowerDNS development began in 1999 as an attempt to provide DNS-based geographic load balancing. The company’s official history says the initially closed-source software was released as open source in 2002.

The Authoritative Server became one part of a wider PowerDNS family that also includes the Recursor and dnsdist. Its distinguishing architecture places authoritative DNS logic in the server while interchangeable backends retrieve records from the selected datastore.

Adoptionsgeschichte

PowerDNS says the software became open source in 2002. The Authoritative Server subsequently found a durable role among hosting providers and other operators that benefit from database-backed DNS administration.

Wie es verwendet wird

Operators use pdns_server to answer authoritatively for managed zones, pdnsutil for zone and DNSSEC administration, and pdns_control for a running server.

Settings reside in pdns.conf or are supplied on the command line. The configuration directory is usually /etc/powerdns but is determined at build time; API keys and backend connection secrets may therefore reside in the same configuration file.

Warum Paket-Nerds sich dafür interessieren

PowerDNS is a notable alternative to zone-file-centered authoritative servers: its backend interface lets packaged deployments connect DNS service to SQL databases, BIND-format zones, and other storage systems.

Its packaging is operationally interesting because backend modules, database schemas, DNSSEC support, service configuration, and the accompanying pdnsutil and pdns_control commands all affect what an installation can do.

Zeitleiste

1999: PowerDNS development began around DNS-based geographic load balancing.
2002: PowerDNS was released as open-source software.
Later development: The Authoritative Server became part of a suite with Recursor and dnsdist.

Related projects

PowerDNS Recursor provides recursive resolution rather than authoritative hosting, while dnsdist distributes and filters DNS traffic in front of DNS servers.

Quellen

Sicherheitslage

Risikostufe: orange

formula declares a Homebrew service.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

formula declares a Homebrew service

Signale

metadata:service

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Formelmetadaten deklarieren einen Service- oder Daemon-Block.
Homebrew-Bottle-Metadaten sind für 5 Plattformziele verfügbar.
Installiert mit 4 Laufzeitabhängigkeiten.
Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: /etc/powerdns/pdns.conf${config-dir}/pdns.conf

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: /etc/powerdns/pdns.conf${config-dir}/pdns.conf

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit
`pdns_control`	cli	globales Executable
`pdns_server`	cli	globales Executable
`pdnsutil`	cli	globales Executable
`zone2json`	cli	globales Executable
`zone2sql`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-11-04

Manager-Version5.1.5

Manager aktualisiert2026-10-21

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

https://www.powerdns.com

InfoRelease/tag comparison is only available for GitHub repositories.https://www.powerdns.comnone Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:pdns
Version	5.1.5
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/pdns
Homepage	https://www.powerdns.com
Repository	https://github.com/powerdns/pdns
Upstream-Dokumentation	https://www.powerdns.com
Lizenz	GPL-2.0-or-later
Quellarchiv	https://downloads.powerdns.com/releases/pdns-5.1.5.tar.bz2
Zuletzt aktualisiert	2026-10-21T12:28:11Z
Pulse	updated
Abhängigkeiten	boost, lua, openssl@4, sqlite
Build-Abhängigkeiten	pkgconf
Von macOS bereitgestellte Bibliotheken	curl
Bottle	verfügbar (auf arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	declared

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	pdns
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

pdns-backend-bind 4.9.16-0+deb13u1

BIND backend for PowerDNS