diver3923 4 Posted ... This post was prompted by Air's announcement that US Netflix is working again when using their DNS servers. Thanks for that effort! I use pfSense and have it configured to use DNS Resolver through an AirVPN server. All clients get their DNS from pfSense. My understanding is that Resolver goes straight to the root servers and does not contact an external DNS server for queries. In order to take advantage of the routing benefits of using Air DNS servers (such as getting US Netflix from European servers) should I be using DNS Forwarder instead of Resolver? Does Resolver defeat the microrouting (not sure if that is the correct term) of the Air DNS servers? ipleak.net shows only the AirVPN DNS server, but that might not matter if pfSense is going straight to the root servers. Thanks Quote Share this post Link to post
go558a83nk 362 Posted ... This post was prompted by Air's announcement that US Netflix is working again when using their DNS servers. Thanks for that effort! I use pfSense and have it configured to use DNS Resolver through an AirVPN server. All clients get their DNS from pfSense. My understanding is that Resolver goes straight to the root servers and does not contact an external DNS server for queries. In order to take advantage of the routing benefits of using Air DNS servers (such as getting US Netflix from European servers) should I be using DNS Forwarder instead of Resolver? Does Resolver defeat the microrouting (not sure if that is the correct term) of the Air DNS servers? ipleak.net shows only the AirVPN DNS server, but that might not matter if pfSense is going straight to the root servers. Thanks I found all the DNS stuff to be overcomplicated. So, I turned off resolver and forwarder and pass to my DHCP clients the DNS I want them to use. That could be 10.4.0.1 (AirVPN DNS). Then I use firewall rules to allow 10.4.0.1 and block all other DNS. It simplified my life greatly. Quote Share this post Link to post