DNS Resolver issue? NordVPN and Netflix Alias not working
Hey all I have an issue that I've finally swallowed that pride pill and am now reaching out for help. :)
I am running pfsense with pfblockerNG. I've already set up the rules to direct any LAN traffic going to the Aliases to WAN. This works and bypasses the VPN like it's supposed to. I've verified with the tracert. Outbound NAT rules are all the same for each interface x.x.x.x/24 Port * Dest * NAT Address WAN/LAN NAT Port *
I have one machine that all traffic avoids VPN. Netflix - no problems. I can browse, ping, stream. All the good things.
When I run a nslookup netflix.com from the machine outside of VPN I get:
Server: google-public-dns-a.google.com Address: 8.8.8.8
Non-authoritative answer: Name: netflix.com Addresses: 2620:108:700f::36c9:787a 2620:108:700f::36ba:81ef 2620:108:700f::36c9:e71f 2620:108:700f::36c8:3e87 2620:108:700f::36bf:e787 2620:108:700f::36bf:504c 2620:108:700f::3695:afe4 2620:108:700f::36bb:1240 52.35.157.101 52.35.127.145 52.36.254.166 52.34.191.89 52.35.242.187 52.35.41.86 52.35.68.39 52.34.244.169
IF the machine is behind the pfsense/pfblockerNG (even though all traffic routes to WAN) I get the following:
Server: google-public-dns-a.google.com Address: 8.8.8.8
Name: netflix.com Address: 104.250.104.10
No machines that are using the routing rules can access. Netflix. Can ping, and tracert but cannot browse or stream.
I've tried disabling the DNS Resolver, Rebooting, CMD: unbound-control -c /var/unbound/unbound.conf dump_cache | grep netflix.com,
No luck what so ever. I would be a very happy man if someone could shove me in the right direction and tell me what my tired eyes are missing. Thanks in advance!
Posted Aug 17, 2017, 7:49 PM UTC