Neflix blocks access to its content if you connect via tunnelbroker.net.
I could search the internet for the IPv6 net ranges that netflix uses, but these are operated by AWS and may change at any time. Bad.
My simple and non-intrusive solution: since I already use a local nameserver (bind9) in my LAN, why not configure it so that it returns no AAAA addresses for netflix? There is a statement: filter-aaaa-on-v4
that does the trick. Unfortunately, one cannot use this setting per zone, it is a global setting.
My solution: forward all queries for netflix.com to another nameserver that has filter-aaaa-on-v4
set.
My main server configuration:
zone "netflix.com" { type forward; forward only; forwarders { 192.168.1.91; }; };
And on 192.168.1.91:
options { directory "/var/cache/bind"; filter-aaaa-on-v4 yes; recursion yes; forwarders { 8.8.8.8; 8.8.4.4; }; forward only; };
That’s it!
2 Comments
Add a Comment