HOWTO: Set Up PowerDNS with Split-Horizon Resolution¶
Split-horizon DNS is how HybridOps services maintain consistent names across on-prem, Hetzner, and GCP — with internal resolution pointing to private IPs and external or DR resolution pointing to the appropriate public or cloud endpoints. This HOWTO covers deploying PowerDNS with zone-view configuration, populating the internal and external views for the core platform services, validating resolution from each network context, and wiring the PowerDNS API for DR cutover automation.
What this covers:
- PowerDNS zone-view configuration for internal (private) and external (public/DR) resolution paths
- Core platform service DNS records across both views: NetBox, Prometheus, application endpoints
- PowerDNS API integration for automated DR record updates during failover