IPv6 HE tunnel broker and Netflix quick fix idea
-
Hello fellow Netgate community members can you please help,
With IPv6 and hurricane electric tunnel broker service I have noticed that I'm having issues accessing Netflix services. It seems that my issue would resolve itself if I could add a custom option into Unbound's DNS resolver, such that unbound would specifically see the domain Netflix and know to only resolve to A dns records. Simply put configure Unbound resolver to ignore AAAA dns records for a specific domain name. I know there's a way to do this again, again I need the actual specific custom line entry directives. This would resolve streaming service issues very quickly if we could pass through the request and specifically direct what DNS should resolve to as needed.
Can anyone confirm the following example?
server: dns64-ignore-aaaa: netflix.com dns64-ignore-aaaa: netflix.net dns64-ignore-aaaa: nflxext.com dns64-ignore-aaaa: nflxso.net dns64-ignore-aaaa: nflxvideo.net dns64-ignore-aaaa: www.netflix.com -
This fixed my issues 100% anyone else parse AAAA and A dns records like this?
-
@JonathanLee said in IPv6 HE tunnel broker and Netflix quick fix idea:
This fixed my issues 100% anyone else parse AAAA and A dns records like this?
That issue is very old.
Hit the search button - its just above :
The issue has even a pfBlockerng solution made for it :
Check the check box.
Add all the host names that should not be resolved to AAAA.
Done.
