unbound not working with Nest and Echo 4th Gen

Started by knight2f6, March 03, 2024, 06:56:47 PM

Previous topic - Next topic
Hi Everyone, I have a strange situation where Unbounds works perfectly, except when it comes to Nest website and *one* of my Amazon echos.

Background: I have OPNsense with Zenarmor, DHCPv4 and v6, and Unbound activated. My provider is Comcast. Every website and app works perfectly except for two. I cannot get my Nest app to connect to outside and my echo 4th gen would not connect either. If I disable Unbound, everything works just fine. I have NO rules, no blacklists, and nothing fancy going on with Unbound. Just a simple redirect to Comcast's DNS servers.

I have 5 amazon echos in my environment. Four are echo dots, and they work perfectly. The issue is only with this one echo 4th gen.

How do I troubleshoot this? I looked at the log files for Unbound and there is nothing there. Appreciate any insight here.
thanks

OK, figured it out. I am posting this for others, in case they have the same issue, or if someone from OPNsense or NLnet is monitoring these.

there is an issue with DNS64, the sythesized response is not getting accepted by my phone, latest iPhone, or Echo 4th gen. the reason that othe Alexa devices in my network did not have any problem, is probably because they are old and don't do v6. I turned off the DNS64 conversion and everything started to work.

I am assuming, perhaps erroneously, that because it is Apple and Amazon, the issue is likely in the Unbound. But would not be surprized if both companies mis-implemented their IPv6 stack.

Anyways, I hope this helps someone.

DNS64 is not a standalone feature, it needs NAT64 to work. Does your ISP provide NAT64? Or did you configure your own?

And how is NLnet relevant in this context?

Cheers
Maurice
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).