# Able to issue against CNAME, but not the actual server

**URL:** <https://community.letsencrypt.org/t/able-to-issue-against-cname-but-not-the-actual-server/127948>\
**Category:** Help\
**Created:** [July 8, 2020, 7:55pm UTC](https://community.letsencrypt.org/t/able-to-issue-against-cname-but-not-the-actual-server/127948 "2020-07-08T19:55:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [July 8, 2020, 8:08pm UTC](https://community.letsencrypt.org/t/able-to-issue-against-cname-but-not-the-actual-server/127948/2 "2020-07-08T20:08:00Z")

</div>

The site [unboundtest.com](http://unboundtest.com) has some errors (timeouts) in its results: [https://unboundtest.com/m/A/myproxy.ccs.ornl.gov/BN7BGJVH](https://unboundtest.com/m/A/myproxy.ccs.ornl.gov/BN7BGJVH)

However, the log messages are quite technical and as I’m not an unbound (the DNS resolver used by Let’s Encrypt by the way) expert, I don’t know how to interpret them.

A possible interesting thread I found: [How to reproduce CAA SERVFAIL? Works for me, doesn't for LE staging or prod](https://community.letsencrypt.org/t/how-to-reproduce-caa-servfail-works-for-me-doesnt-for-le-staging-or-prod/43406/2) Seems to be a matter of [0x20 (capitalization) randomization](https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00) not going correctly.

---

_[View the full topic](https://community.letsencrypt.org/t/able-to-issue-against-cname-but-not-the-actual-server/127948)._