# Domain resolution issue affecting topic embeds

**URL:** <https://meta.discourse.org/t/domain-resolution-issue-affecting-topic-embeds/304868>\
**Category:** Bug\
**Created:** [April 22, 2024, 7:25am UTC](https://meta.discourse.org/t/domain-resolution-issue-affecting-topic-embeds/304868 "2024-04-22T07:25:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [April 22, 2024, 9:39am UTC](https://meta.discourse.org/t/domain-resolution-issue-affecting-topic-embeds/304868/2 "2024-04-22T09:39:19Z")

</div>

It seems ok here on Meta:

> **[OSI’s responds to NTIA on widely available AI models](https://opensource.org/blog/osi-response-to-ntia)**
>
> In addition to joining a number of other organizations in responding to the NTIA’s Request for Comment on, OSI has provided its organizational response to the call for public comment, centering its…

From your description, my guess would be that your server is resolving ipv6 records when making DNS lookups (we use [getaddrinfo](https://github.com/discourse/discourse/blob/b3f119231216d0ddad384960380f335a9f65e8e0/lib/final_destination/resolver.rb#L57) for that). But then when attempting to connect to them, it’s failing.

> [@angus](#):
>
> An `Excon.get` of the original URL will not.

That might be because it tries the ip6 address, fails, and then falls back to the ip4 address. We don’t currently have that kind of fallback logic in `FinalDestination#resolve`:

> <https://github.com/discourse/discourse/blob/b3f119231216d0ddad384960380f335a9f65e8e0/lib/final_destination.rb#L256-L257>

---

_[View the full topic](https://meta.discourse.org/t/domain-resolution-issue-affecting-topic-embeds/304868)._