Force Wireguard DNS Zone Override: Revision history

Jump to navigation Jump to search

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

3 July 2025

  • curprev 17:4117:41, 3 July 2025‎ Maeve talk contribs‎ 1,966 bytes +1,966‎ Created page with "Sometimes you may have a situation in which you require a machine using a Wireguard tunnel to always use a specific DNS server to resolve specific zones. One case where we needed this was an Active Directory DNS zone that also matched a publicly available DNS zone. The publicly available records resolved to one end of a NAT'd IP range, but the AD DNS zone had records pointing to the other side. When connecting locally in the network, this was fine, but some Windows clien..." Tag: Visual edit
Retrieved from "https://www.rosemarknetworks.com/wiki/index.php/Force_Wireguard_DNS_Zone_Override"