Skip to content

Linux DNS not being set as expected. #58

Closed
@bleach86

Description

@bleach86

Trying to run the client example with my values put in as required as well as adding a DNS configuration.

I notice that when it would connect I would not have internet access. I narrowed this down to a DNS issue caused by /etc/resolv.conf not being updated as expected.

Looking at wg-quick I notice that they prefix the interface name with tun..

So modifying configure_dns() and clear_dns() to do the same results in expected behavior of updating /etc/resolv.conf with my values.

The linux wg-quick man page as well as the freebsd wg-quick man page both indicate the same prefixing of the interface name with tun.

This could cause a DNS leak if you allow local networks in your wg config.

This would cause using unexpected DNS if you do not allow local networks, but your '/etc/resolv.conf` contains an IP of a remote host. This could also possibly be a leak as well.

To recreate be on Linux with a wg config with AllowedIPs = 0.0.0.0/0,::/0 and have only LAN IPs in /etc/resolv.conf

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Ready to release

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions