Skip to content

Commit 27a3d64

Browse files
committed
Add details about DNS leakage with NetworkManager for #59
1 parent 35f86c4 commit 27a3d64

File tree

2 files changed

+26
-3
lines changed

2 files changed

+26
-3
lines changed

CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,8 @@ features.
1919
- Change the handling of DOMAIN to support mutiple class, with a change in the
2020
way the values are processed and added to systemd-resolved (@adq)
2121
- Updated the documentation in a number of areas, including a new section
22-
specifically on DNS Leakage, links to the DBus commands, and spelling
23-
corrections, etc.
22+
specifically on DNS Leakage, links to the DBus commands, NetworkManager and
23+
DNSSEC issues, and spelling corrections, etc.
2424
- Now recommended using the `up-restart` option in the configuration files to
2525
ensure that `update-systemd-resolved` is re-run when the connection only
2626
partially restarts (i.e connection restarts, but not the TUN/TAP device).

README.md

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -264,7 +264,30 @@ responsible for routing all queries, and so both links will get all requests.
264264
How to manage the DNS settings of other links while the VPN is operational is
265265
outside the scope of this script at this time.
266266

267-
## DNSSEC Issues
267+
## Known Issues
268+
269+
There are a number of known issues relating to some third-party servers and
270+
services:
271+
272+
### NetworkManager
273+
274+
LP1671606:https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606
275+
LP1688018:https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018
276+
277+
There is currently a regression with versions of NetworkManager 1.2.6 or later
278+
(see [LP#1671606][LP1671606] and [LP#1688018][LP1688018]) which means that it
279+
will automatically set all normal network interfaces with `~.` for DNS routing.
280+
This means that even if you set `dhcp-option DOMAIN-ROUTE .` for your VPN
281+
connection, you will still leak DNS queries over potentially insecure networks.
282+
283+
issue-59:https://github.com/jonathanio/update-systemd-resolved/issues/59
284+
285+
If you are concerned by potentially leaking DNS on systems which use
286+
NetworkManager, you may need to configure an [additional script][issue-59]
287+
into NetworkManager which change the domain routing settings on all non-VPN
288+
interfaces.
289+
290+
### DNSSEC Issues
268291

269292
```shell
270293
$ systemd-resolve eu-central-1.console.aws.amazon.com

0 commit comments

Comments
 (0)