nginx-proxy-manager
nginx-proxy-manager copied to clipboard
Please,add Dynv6 for npm‘s ssl .thx very much!
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
This is already supported. Please use the DNS RFC 2136 challenge for DynV6.
Steps:
- Generate a TSIG key for your zone at https://dynv6.com/keys/tsig/new.
- Follow the guide at https://certbot-dns-rfc2136.readthedocs.io/en/stable/
Edit the credential file, taking care to enter an IP address for dns_rfc2136_server.
In this case, use the output of the command dig +short ns1.dynv6.com, which should now be 95.216.144.82.
The file should look something like this
# Target DNS server (IPv4 or IPv6 address, not a hostname)
# `dig +short ns1.dynv6.net` to get the IP
dns_rfc2136_server = 95.216.144.82
# Target DNS port
dns_rfc2136_port = 53
# TSIG key name (there is a trailing dot . )
dns_rfc2136_name = tsig-xxxxxx.dynv6.com.
# TSIG key secret (this is a dummy key, use your own)
dns_rfc2136_secret = 4q4wM/2I180UXoMyN4INVhJNi8V9BCV+jMw2mXgZw/CSuxUT8C7NKKFsAmKd7ak51vWKgSl12ib86oQRPkpDjg==
# TSIG key algorithm
dns_rfc2136_algorithm = HMAC-SHA512
# TSIG sign SOA query (optional, default: false)
dns_rfc2136_sign_query = false
- Voilà! You're good to go!
Dynv6 may say that the key is never used; this is a bug and you're all set.
dns_rfc2136_name = tsig-xxxxxx.dynv6.com. This works with and without a dot at the end.