# Failure to resolve own domain?

**URL:** <https://meta.discourse.org/t/failure-to-resolve-own-domain/122327>\
**Category:** Product Support\
**Created:** [7월 8, 2019, 2:20오후 UTC](https://meta.discourse.org/t/failure-to-resolve-own-domain/122327 "2019-07-08T14:20:15Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![teward](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/teward/32/148702_2.png) [@teward](https://meta.discourse.org/u/teward)\
**Post date:** [7월 8, 2019, 2:20오후 UTC](https://meta.discourse.org/t/failure-to-resolve-own-domain/122327/1 "2019-07-08T14:20:15Z")

</div>

We run a discourse at [discourse.lubuntu.me](http://discourse.lubuntu.me). It is configured to have that as its base URL.

However, internally, the system is getting 500 errors with its internal certificate.svg links and the discobot builtin for greeting users.

```
SocketError (Failed to open TCP connection to discourse.lubuntu.me:443 (getaddrinfo: Name or service not known))
/usr/local/lib/ruby/2.6.0/net/http.rb:949:in `rescue in block in connect'

```

This is behaving like it’s unable to do a DNS lookup inside the container running Discourse. Is there a way to fix this issue or better debug it?

---

_[View the full topic](https://meta.discourse.org/t/failure-to-resolve-own-domain/122327)._