Closed Nottt closed 2 years ago
Hi, I don't see what the issue is. It seems that unbound works for the both of us; asking unbound for the domain that needs to be redirected results in the configured IPv6. Tested on both the 1.6.7 and latest version here.
Maybe the issue lies with the configuration of your devices. I would be happy to help if you find what the issue is in your case. Maybe a pcap would help to see all the network traffic between your devices and unbound.
Closing this as no-issue and inactivity now; you can ping me here if you want.
I use unbound to redirect domains to a IPV4/IPV6 address.
I can query the correct AAAA record with dig, but when I use the dns server in my devices, they won't work.
I tested using dnschef, to see which records are being queried by the device, and it looks up A and AAAA records. When I use dnschef to change the response to my ipv4/ipv6 address, the device works just fine as expected. With unbound it doesn't.
So I can rule out issues with my ipv6 configuration in the server. Also the ipv6 address works fine in chrome, as expected.
my configuration is
My IPs are public reachable in the internet, and are not local. Version: 1.6.7-1ubuntu2.3.
For now I have to use dnschef instead of unbound, because the devices work fine with it but with unbound it gets bad IPV6 data somehow :(