# Letsencrypt for subdomain

**URL:** <https://community.letsencrypt.org/t/letsencrypt-for-subdomain/99504>\
**Category:** Help\
**Created:** [August 9, 2019, 10:23am UTC](https://community.letsencrypt.org/t/letsencrypt-for-subdomain/99504 "2019-08-09T10:23:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajan.shah](https://avatars.discourse-cdn.com/v4/letter/r/8e8cbc/32.png) [@rajan.shah](https://community.letsencrypt.org/u/rajan.shah)\
**Post date:** [August 9, 2019, 10:23am UTC](https://community.letsencrypt.org/t/letsencrypt-for-subdomain/99504/1 "2019-08-09T10:23:00Z")

</div>

Can I create certificate for internal sub domain using letsencrypt which is not availble in public? But its main domain available in public.

like [example.com](http://example.com) is available in public but [xyz.example.com](http://xyz.example.com) is not accessible in public and getting from openstack or internal dns

As i am getting error that  
Detail: dns :: DNS problem: NXDOMAIN looking up A for

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [August 9, 2019, 10:26am UTC](https://community.letsencrypt.org/t/letsencrypt-for-subdomain/99504/2 "2019-08-09T10:26:38Z")

</div>

It’s possible if you use DNS validation. In that case, you would need to be able to automatically create a _public_ TXT record for `_acme-challenge.xyz.example.com` when you issue or renew the certificate.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 8, 2019, 10:26am UTC](https://community.letsencrypt.org/t/letsencrypt-for-subdomain/99504/3 "2019-09-08T10:26:40Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.