Hi  @Theedoek 

It's for both of you.

We have identified a similar issue. But that specific issue has a prerequisite: using dual-stack IPv4 and IPv6, which is the case of Mr. @SuperUserOne

Now that you don't use IPv6 at all, we will investigate your feedback further. Will keep you posted once we get any updates. Thanks for your feedback.

Theedoek wrote

Vincent-TP wrote

Hi  @SuperUserOne 

 

Sorry, I mixed you up with another user—please disregard.

 

We’ve identified the cause of the DNS issue you reported and are currently discussing a solution.

 

  @Vincent-TP 

I assume this message is for me then (OP of this topic)?

Hi  @Theedoek 

Root Cause Analysis:
Netflix is highly sensitive to DNS resolution, and this issue is likely caused by the DNS64 mechanism.
Even if you are not using IPv6, when a device queries a domain name and receives an IPv4 address, DNS64 may still synthesize an IPv6 address (AAAA record) and return it to the client.

Description of the Issue:
When this occurs in the TV’s Netflix client, the actual process is as follows:

1. DHCP → Obtains DNS = Gateway.
2. Netflix requests the domain name.
3. DNS64 returns a synthesized IPv6 address (AAAA record).
4. The Netflix client attempts to stream via IPv6.
5. However, the actual network has no IPv6 routing and no NAT64 in place.

As a result, functions like API calls or login may still work over IPv4, making it appear to the user that they can log in and browse but cannot play videos. This issue aligns with the DNS-related problem I talked with @SuperUserOne.

Solution:
We are preparing to resolve this issue through a firmware update. Please stay tuned for further updates.

  @Vincent-TP 

Thank you for clarifying Vincent.

I did see quite a few similarities between my post and SuperUserOne's post.

Let's see what a firmware update will bring us!