Closed bremme closed 6 months ago
Are you adding the sub domain as an actual domain in DirectAdmin?
This I believe is the only way it will work.
I added the subdomain just as a DNS entry on the main domain. You're saying that I need to add local.example.com
as a completely separate domain to example.com
?
After I posted this issue I changed my nameservers to Cloudfare to see if that solved my issues. But ran into the exact same problem. I did came up with a solution:
_acme-challenge.local.example.com CNAME _acme-challenge.local
Where I use a CNAME to point the name Certbot is looking for to the record Certbot actually creates. I'm pretty sure this would also work when using direct admin. But I guess your solution is probably the right way to go.
I guess we can close this issue for now if its expected behavior right?
Yes, I did suggest adding the subdomain as a domain in directadmin. That will allow things to work fine. Had another user who reported this same situation ages ago.
Nice you found a workaround.
But yes, I think we close this as working as it should.
Sounds good, I'll close this issue. Thanks for you quick responses.
I'm not totally sure if this is a bug, expected behavior or a configuration error on my end. This is what I'm trying to achieve (while following this guide https://www.youtube.com/watch?v=qlcVx-k-02E).
I have added a wildcard sub-sub domain which points to a local ip:
I also tried a couple different variations like
When I use
ping something.example.com
I get my configured local ip back. So far so good. But the DNS challenge fails with an error:The main issues seems that the record that is created is:
While certbot seems to be looking for
_acme-challenge.local.example.com
.How can I solve this issues? Let me know if you need any more information.