Project

General

Profile

Actions

Feature #16686

open

Better handling DNS when using multiple wireguard tunnels of different locations

Added by Tam N 1 day ago. Updated 1 day ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

Hello,

I'm not very technical but here goes:

Feature request: An option to make it so each wireguard tunnel uses its own interface/tunnel for DNS. And/or also, allow gateway groups under System -> General Settings -> DNS Server Settings drop down menu and/or Interface groups (like gateway groups) under Services -> DNS Resolver -> Outgoing Network Interfaces

Why?

  • Let's say you have multiple wireguard tunnels created with different locations. For example: Paid Mullvad VPN service. Wireguard tunnel #1 in pfsense: USA, Dallas location. Wireguard tunnel #2: UK, Glasgow location.
  • From my knowledge, under setting: Services -> DNS resolver -> Outgoing Network Interfaces; you must pick which wireguard tunnel interface to use to contact a DNS server. So for example, you can select USA Dallas WG interface, UK Glasgow WG interrace or both of them. This is with "Enable Forwarding Mode" enabled.
  • A client using a wireguard tunnel will be requesting DNS from a mis-matching DNS server (or many mis-matching DNS servers) and stick out like a sore thumb for privacy/fingerprinting; depending on which outgoing network interfaces you have selected in pfsense dns resolver settings.

For example, client is using USA Dallas wireguard tunnel. But their DNS will be using USA Dallas interface AND UK Glasgow interface locations for their DNS server. (if both were selected under Outgoing Network Interaces)

  • This makes it impossible (or almost impossible) to setup DNS properly using multiple wireguard tunnels of different locations.
  • Also, if I only select one outgoing network interface - I believe it creates a single point of failure. If a server from that mullvad tunnel goes down, all internet will go down. But, if I select multiple outgoing network interfaces, they will all be used for DNS on each client.
Actions #1

Updated by Tam N 1 day ago

To add one more thing:

It would be good to have redundancy in dns so that if the proper dns server location ever goes down, it would be acceptable to temporarily fall back to a mis-matched dns server location until the proper dns goes back up

Actions

Also available in: Atom PDF