# Desktop Central Support **URL:** \ **Category:** Help\ **Created:** [March 12, 2019, 5:27pm UTC](https://community.letsencrypt.org/t/desktop-central-support/88514 "2019-03-12T17:27:03Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![SeTec\_Astronomy](https://avatars.discourse-cdn.com/v4/letter/s/c89c15/32.png) [@SeTec\_Astronomy](https://community.letsencrypt.org/u/SeTec_Astronomy)\ **Post date:** [March 12, 2019, 5:27pm UTC](https://community.letsencrypt.org/t/desktop-central-support/88514/1 "2019-03-12T17:27:03Z")
I am just starting to investigate setting up Let’s Encrypt for our Desktop Central server. This server is installed on a Windows 2012 server. I believe it runs on Apache. Right now it only has an internal domain with a .local as it’s not set up for external internet access. Has anyone set up Let’s Encrypt on Desktop Central? Again I’m brand new on this so looking for some guidance or just confirmation that it’s even possible. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [March 12, 2019, 5:47pm UTC](https://community.letsencrypt.org/t/desktop-central-support/88514/2 "2019-03-12T17:47:56Z")
Hi @SeTec_Astronomy > [@SeTec\_Astronomy](#): > > Right now it only has an internal domain with a .local you can't create a certificate with .local as the last part of the domain name. If you want a public trusted certificate, you need a public visible domain name which ends with an entry of the Public Suffix List: [https://publicsuffix.org/list/public\_suffix\_list.dat](https://publicsuffix.org/list/public_suffix_list.dat) The domain name must be unique - worldwide. So Letsencrypt is able to check you are the owner of that domain. ---
**Author:** ![SeTec\_Astronomy](https://avatars.discourse-cdn.com/v4/letter/s/c89c15/32.png) [@SeTec\_Astronomy](https://community.letsencrypt.org/u/SeTec_Astronomy)\ **Post date:** [March 12, 2019, 5:54pm UTC](https://community.letsencrypt.org/t/desktop-central-support/88514/3 "2019-03-12T17:54:44Z")
We own [itcuso.com](http://itcuso.com) which is accessible world wide. Currently that website is hosted at GoDaddy. Could we use that domain? ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [March 12, 2019, 5:58pm UTC](https://community.letsencrypt.org/t/desktop-central-support/88514/4 "2019-03-12T17:58:16Z")
> [@SeTec\_Astronomy](#): > > We own [itcuso.com](http://itcuso.com) which is accessible world wide Yes, that's the typical situation. Create an A (ipv4) or / and an AAAA (ipv6) DNS record with the ip address / addresses of your server. Then update your server that a running webserver answers, if you go to ```nohighlight http://itcuso.com ``` with your browser. ---
**Author:** ![SeTec\_Astronomy](https://avatars.discourse-cdn.com/v4/letter/s/c89c15/32.png) [@SeTec\_Astronomy](https://community.letsencrypt.org/u/SeTec_Astronomy)\ **Post date:** [March 12, 2019, 6:03pm UTC](https://community.letsencrypt.org/t/desktop-central-support/88514/5 "2019-03-12T18:03:56Z")
Currently we have [www.itcuso.com](http://www.itcuso.com). So would we make a wildcard cert with Let’s Encrypt so it works for the [www.itcuso.com](http://www.itcuso.com) and any other combinations like [https://dc.itcuso.com](https://dc.itcuso.com) which doesn’t exist yet? Is there a guide for setting up Let’s Encrypt for a scenario like this? Appreciate your help. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [March 12, 2019, 7:07pm UTC](https://community.letsencrypt.org/t/desktop-central-support/88514/6 "2019-03-12T19:07:05Z")
If you want a wildcard, you must use dns-01 validation. So you don't need a running webserver, instead you have to create a dns TXT entry. > [@SeTec\_Astronomy](#): > > Is there a guide for setting up Let’s Encrypt for a scenario like this? Start there: > **[How It Works - Let's Encrypt](https://letsencrypt.org/how-it-works/)** > > The objective of Let’s Encrypt and the ACME protocol is to make it possible to set up an HTTPS server and have it automatically obtain a browser-trusted certificate, without any human intervention. This is accomplished by running a certificate... ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [April 11, 2019, 7:07pm UTC](https://community.letsencrypt.org/t/desktop-central-support/88514/7 "2019-04-11T19:07:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.