Package Details: dns01proxy-desec 0.1.8-1

Git Clone URL: https://aur.archlinux.org/dns01proxy.git (read-only, click to copy)
Package Base: dns01proxy
Description: ACME DNS-01 proxy server
Upstream URL: https://github.com/liujed/dns01proxy
Licenses: Apache-2.0
Conflicts: dns01proxy-acmedns, dns01proxy-acmeproxy, dns01proxy-alidns, dns01proxy-all-inkl, dns01proxy-azure, dns01proxy-bunny, dns01proxy-cloudflare, dns01proxy-cloudns, dns01proxy-conoha, dns01proxy-digitalocean, dns01proxy-directadmin, dns01proxy-dnsimple, dns01proxy-dode, dns01proxy-domainnameshop, dns01proxy-duckdns, dns01proxy-dynu, dns01proxy-dynv6, dns01proxy-easydns, dns01proxy-edgeone, dns01proxy-gandi, dns01proxy-gcore, dns01proxy-glesys, dns01proxy-godaddy, dns01proxy-googleclouddns, dns01proxy-he, dns01proxy-hetzner, dns01proxy-huaweicloud, dns01proxy-infomaniak, dns01proxy-inwx, dns01proxy-ionos, dns01proxy-linode, dns01proxy-loopia, dns01proxy-luadns, dns01proxy-mailinabox, dns01proxy-metaname, dns01proxy-mijnhost, dns01proxy-mythicbeasts, dns01proxy-nanelo, dns01proxy-netcup, dns01proxy-netlify, dns01proxy-nfsn, dns01proxy-njalla, dns01proxy-ovh, dns01proxy-porkbun, dns01proxy-powerdns, dns01proxy-rfc2136, dns01proxy-route53, dns01proxy-scaleway, dns01proxy-simplydotcom, dns01proxy-spaceship, dns01proxy-tencentcloud, dns01proxy-transip, dns01proxy-vultr, dns01proxy-westcn
Submitter: liujed
Maintainer: liujed
Last Packager: liujed
Votes: 0
Popularity: 0.000000
First Submitted: 2025-06-11 19:21 (UTC)
Last Updated: 2025-11-22 22:56 (UTC)

Latest Comments

liujed commented on 2025-11-23 15:51 (UTC) (edited on 2025-11-23 15:51 (UTC) by liujed)

This proxy is basically a wrapper around Caddy, and uses DNS providers written by the Caddy community. Due to limitations in Go's plugin framework, Caddy uses custom-built binaries, based on the Caddy packages you want to use. Compiling in a DNS provider (or any other Caddy package) causes the provider's initialization code to run during startup, even if the provider is not used in Caddy's configuration.

By having a separate AUR package for each provider, we reduce the amount of trusted code in each package. This way, a user only needs to audit / worry about / trust code from a single community-contributed DNS provider instead of all of them.

If there's an approach that achieves the above and avoids having N different AUR packages, I'm all ears! 😅

tippfehlr commented on 2025-11-22 23:01 (UTC) (edited on 2025-11-22 23:14 (UTC) by tippfehlr)

Why do you need separate conflicting packages for every provider? This doesn’t seem right.

edit: ok, these are all just configurations for your proxy. Please upload the proxy as one package.