teneff
New Around Here
My current setup:
In NameCheap I have configured both home and *.home as A + Dynamic DNS Record .
In Asus Merlin UI -> WAN -> DDNS I have set Server: NAMECHEAP.COM, Hostname: home.domain.tld, Domain Name: *.home.domain.tld and Enable wildcard: Yes.
Everything seems to be working, but the certificate generated is only issued to CN: home.domain.tld. Isn't that Enable wildcard options exactly for issuing wildcard certificate? Have anyone managed to issue such certificate?
I have also tried copying /etc/inadyn.conf to /jffs/configs/inadyn.conf changing the hostname to
as described in the in-a-dyn docs but it doesn't seem to have an effect on the letsencrypt certificate request
- Asus router RT-AX88U
- Merlin installed
- NameCheap domain
- Dynamic IP
- DDSN configuration with NameCheap (working)
- Obtain *.home.domain.tld certificate
- Configure nginx reverse proxy + HTTPS for multiple
In NameCheap I have configured both home and *.home as A + Dynamic DNS Record .
In Asus Merlin UI -> WAN -> DDNS I have set Server: NAMECHEAP.COM, Hostname: home.domain.tld, Domain Name: *.home.domain.tld and Enable wildcard: Yes.
Everything seems to be working, but the certificate generated is only issued to CN: home.domain.tld. Isn't that Enable wildcard options exactly for issuing wildcard certificate? Have anyone managed to issue such certificate?
I have also tried copying /etc/inadyn.conf to /jffs/configs/inadyn.conf changing the hostname to
Code:
hostname = { 'home.domain.tld', '*.home.domain.tld' }as described in the in-a-dyn docs but it doesn't seem to have an effect on the letsencrypt certificate request
Last edited:
