Jump to content

- - - - -

Force All Network Interfaces for DNS


  • Please log in to reply
No replies to this topic

#1 B00ze



  • Members
  • Pip
  • 2 posts

Posted 16 October 2017 - 02:50 AM

Good day.


Today I updated my AirVPN client from 2.10 -> 2.13.


Played around with settings (the new UI needs to be wider than before to show all fields in the server list) then connected...


To my surprise, my Windows Firewall Notifier tool (which opens a pop-up for blocked connections) started popping-up non-stop; the Windows DNS Client and other Windows Services were all trying to get DNS resolution from my router (the normal DNS address is the router on my system). This wasn't happening with previous AirVPN client.


Started looking for the source of the problem and found that the DNS entry in my normal network adapter had not been changed to AirVPN's, as it was with the older Eddie client. AirVPN had apparently configured the Windows Filtering Platform to correctly block DNS queries to anything but the AirVPN servers (which triggered a Blocked-Connection event, which made Windows Firewall Notifier open a pop-up.) And for some reason Windows kept on querying the non-VPN DNS server. This was really annoying, since I could not create a firewall rule to block access to the regular DNS (thereby silencing the Windows Firewall Notifier tool) because then I would not have been able to resolve DNS when the AirVPN client wasn't running.


Went into Advanced Options in Eddie and found this "Force All Network Interfaces for DNS" -> Woohoo, problem resolved!


Please make sure this option doesn't get deprecated in future Eddie clients; without this I would have to manually edit the DNS entry of my NIC every time I connected the VPN.


Thank you.

Best Regards,

Similar Topics Collapse

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

Servers online. Online Sessions: 14057 - BW: 52637 Mbit/sYour IP: Access.