<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Sep 12, 2017, at 1:10 PM, Mark Saad <<a href="mailto:mark.saad@ymail.com" class="">mark.saad@ymail.com</a>> wrote:</div><div class=""><div class=""><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;" class=""></div></div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;" class=""><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;" class="">one issue i've had with let's encrypt is trying to use it on private <br class="">subdomains on AWS. iirc the system needs to have a public DNS entry as <br class="">well as access from the internet to work - i might be mistaken tho on <br class="">this...<br class=""></div></div></div></div></blockquote></div><div class=""><br class=""></div>I have LE certs for RFC 1918 addresses. The DNS server I use to validate is a public DNS server, but where<div class="">you user the cert is not relevant.<br class=""><div class=""><br class=""></div><div class=""><div class=""><div>-- <br class="">Dan Langille - BSDCan / PGCon<br class=""><a href="mailto:dan@langille.org" class="">dan@langille.org</a><br class=""><br class=""></div></div><br class=""><div><blockquote type="cite" class=""></blockquote></div></div></div></body></html>