PMG 8.2.6: /etc/pmg/node.conf missing — how to set DNS validation alias for PowerDNS (CNAME -> TXT)?

tanukey

New Member
Jan 15, 2026
1
0
1
Hello,
I’m running Proxmox Mail Gateway 8.2.6 and I want to use DNS-01 (Let’s Encrypt) via PowerDNS. The official 8.2 documentation says to set an alias in /etc/pmg/node.conf:
set the alias property in the Proxmox Mail Gateway node configuration file /etc/pmg/node.conf to domain2.example
My setup:
  • Primary domain: domain1.example (public DNS has CNAME _acme-challenge.domain1.example -> _acme-challenge.domain1.acme.example)
  • PowerDNS manages domain1.acme.example and is accessible via its API from the PMG host
  • Goal: let PMG perform DNS-01 validation by targeting the PowerDNS-managed name (domain1.example) via an alias setting
Problem:
  • /etc/pmg/node.conf does not exist on my system, and I cannot find any equivalent file. I searched for node.conf and related references but found nothing relevant.
What I have already checked:
  • PMG version: 8.2.6
  • Searched common paths for node.conf and code.conf (no hits)
  • Confirmed PowerDNS API is reachable from the PMG host
Questions:
  1. In PMG 8.2.6, where is the node configuration (alias) expected to be set? Is /etc/pmg/node.conf still the correct location or has the file/parameter moved?
  2. If the file no longer exists by default, is it safe/correct to create /etc/pmg/node.conf manually? If so, what is the exact expected format/syntax (example)?
    • e.g. is a plain key=value line such as: alias=domain1.acme.example acceptable, or is a different format required (JSON, INI, etc.)?
  3. After creating/updating the file, which services should be restarted for PMG to pick up the alias? Any specific log entries I should look for to confirm it’s used for ACME validation?
  4. Are there alternative GUI or CLI methods in 8.2.6 to configure this alias for DNS validation (instead of editing a file)?
  5. Is this a known issue/bug in 8.2.6 (missing docs vs implementation), and is there an upstream patch or recommended workaround?
  6. Any caveats regarding permissions/ownership for the file (owner, mode) or SELinux/AppArmor contexts I should consider?