# Alias domain for devices on resindevice.io

**URL:** <https://forums.balena.io/t/alias-domain-for-devices-on-resindevice-io/995>\
**Category:** Product support\
**Created:** [May 22, 2017, 4:11pm UTC](https://forums.balena.io/t/alias-domain-for-devices-on-resindevice-io/995 "2017-05-22T16:11:25Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jmarshall](https://avatars.discourse-cdn.com/v4/letter/j/7993a0/32.png) [@jmarshall](https://forums.balena.io/u/jmarshall)\
**Post date:** [May 23, 2017, 11:03pm UTC](https://forums.balena.io/t/alias-domain-for-devices-on-resindevice-io/995/4 "2017-05-23T23:03:52Z")

</div>

hey Jack (good Name FYI)

we had spotted that and had Just tried to CNAME a domain we have to [resindevice.io](http://resindevice.io) and passing the Device UUID intact. we had a Public DNS CNAME record for .example.com to .resindevice.io and no joy not even an invalid Common Name error from the Cert. I’ll retest as i need to get the CNAME reinstated as we have replaced that device now.

Ideally we would do this in production with a DNAME record.

i can see the reasoning behind using a reverse proxy but i would really like to see at least TLS Client Auth on the inside of the reverse proxy to [resindevice.io](http://resindevice.io) TLS Server. sadly though that wouldn’t answer my concerns on [Open https via public URL](https://forums.balena.io/t/open-https-via-public-url/994/5?u=jmarshall)

The ability to do that and use a DNAME would be a graceful solution to accessing devices’s web interface as an end/nontech user. all without having to worry about things like inward permissions and NAT Traversal that are the standard on most networks today.

Jack

---

_[View the full topic](https://forums.balena.io/t/alias-domain-for-devices-on-resindevice-io/995)._