Netflix and IPv6 via tunnelbroker

Neflix blocks access to its con­tent if you con­nect via tunnelbroker.net.
I could search the inter­net for the IPv6 net ran­ges that net­flix uses, but the­se are ope­ra­ted by AWS and may chan­ge at any time. Bad.
My simp­le and non-intrusi­ve solu­ti­on: sin­ce I alrea­dy use a local name­ser­ver (bind9) in my LAN, why not con­fi­gu­re it so that it returns no AAAA addres­ses for net­flix? The­re is a state­ment: filter-aaaa-on-v4 that does the trick. Unfor­tu­n­a­te­ly, one can­not use this set­ting per zone, it is a glo­bal set­ting.
My solu­ti­on: for­ward all que­ries for netflix.com to ano­t­her name­ser­ver that has filter-aaaa-on-v4 set.

My main ser­ver con­fi­gu­ra­ti­on:

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!

0

1 Comment

Add a Comment

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.