*** This bug is a duplicate of bug 1754671 ***
https://bugs.launchpad.net/bugs/1754671
** This bug is no longer a duplicate of bug 1688018
DNS server from vpn connection is not being used after network-manager
upgrade to 1.2.6
** This bug has been marked a duplicate of bug 1754671
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
** This bug has been marked a duplicate of bug 1688018
DNS server from vpn connection is not being used after network-manager
upgrade to 1.2.6
--
You received this bug notification because you are a
Sadly, the option block-outside-dns is only supported on Windows
clients. Which is a real shame, because systemd-resolved is leaking DNS
queries everywhere by design. This is a problem with the hardcoded
design of the gnome network manager integrating (or rather...not
integrating) with
Jordi:
To me it seems that the problem is that the update-resolv-conf script
was designed to work with pure dnsmasq and not systemd-resolved (used
since 16.10).
I googled around and found somebody has made an update-systemd-resolved
script to replace the update-resolv-conf script when
And still adding further input (in hopes it's useful) when this time I
tested activating the UFW and the CLI client while the network-manager-
openvpn applet was still ON the rogue DNS server appears once again.
Keep in mind that this shouldn't really be on any of the configuration
files at all.
I have kept testing this and the issue has been resolved. Now it should
be matter of integrating this on a branch? As I pointed out on #17 the
OpenVPN dev team has already a branch that should solve this. Let me
know if I'm wrong.
** Changed in: openvpn (Ubuntu)
Status: Incomplete =>
And finally, it seems there was already some work in progress for this
in one of the branches on openvpn github up until recently:
https://github.com/OpenVPN/openvpn/blob/release/2.4/src/openvpn/block_dns.c
Branch: Release/2.4
--
You received this bug notification because you are a member of
Hi,
I actually needed another thing too for getting rid of all the
references to the 8.8.8.8 DNS:
First:
tux@tuxedo:/var/log$ ss | grep 8.8.8
u_str ESTAB 0 0 @/tmp/.X11-unix/X0 285858*
284387
u_str ESTAB 0 0 * 284387
Hi,
I actually needed another thing too for getting rid of all the
references to the 8.8.8.8 DNS:
First:
tux@tuxedo:/var/log$ ss -psaux | grep 8.8.8.
u_str ESTAB 0 0 @/tmp/.X11-unix/X0 285858*
284387
u_str ESTAB 0 0 *
Hi,
I think I found the reason and the solution for this. I left all the
logs on stdout for a while to see if anything dodgy appeared and at some
point saw this message:
./syslog:May 7 14:16:08 tuxedo systemd-resolved[1434]: Switching to fallback
DNS server 8.8.8.8.
./syslog:May 7 14:28:31
So, as promised, the logs. The only thing I needed to replicate the
issue was to add again a DNS server on the network manager
configuration. I found out that removing it from there + using UFW was
doing the trick (meaning the test didn't crash when tried to resolve
using the alternative DNS
Hi, I have been experiencing this bug with the nm-openvpn applet and
more rarely with the openvpn cli client. Right now I'm havinh a hard
time reproducing it but it still definitely happens. I'kk try to get my
network to the original state before trying to mitigate it because right
now when
Thank you, Seth. I've attempted to begin the conversation here:
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1685391
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652525
Title:
DNS leak
Hello GammaPoint, if your system was working in 16.10 but fails in 17.04
then it'd probably be better for everyone involved if you filed a new
bug report with your information. I suggest trying to answer Mathieu's
questions from this bug directly in the description of the new bug.
Thanks
--
You
I am seeing DNS leaks in 17.04. I had been running 16.10 and the dnsmasq
fix that was released fixed my issue back then. But in Zesty I'm seeing
this problem too and not sure how to resolve it yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This is still happening in 17.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652525
Title:
DNS leak in ubuntu 16.10
To manage notifications about this bug go to:
I went to ipleak.net to test if my ip was leaking and sure enough, I saw
my DNS ip address. Its blocking all other IP address except DNS.
IP Details of 192.168.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Saying "there's a leak" doesn't mean anything. What makes you think it's
the case? What are you looking at to tell it's the case?
Please show the data you're using, preferably with something that looks
like an IP address (even if it's not the exact thing in your
configuration, it should make
Hi Seth,
1) /etc/nsswitch.conf hosts line now reads:
hosts: files mdns4_minimal [NOTFOUND=return] dns
2) rebooted
3) vpn on boot: no leak. (I think same as before)
4) I turn off vpn
5) use a browser
6) close browser
7) start vpn connection
8) open browser again
Still leaking. :(
Eylul, try removing this part: resolve [!UNAVAIL=return]
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652525
Title:
DNS leak in ubuntu 16.10
To manage notifications about this bug go to:
Could you investigate a bit if this may be related to the new systemd-reosolvd
service?
*is not sure exactly how to go about testing this*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652525
Hi, here is what the hosts line of /etc/nsswitch.conf is saying, while
the leak is occuring
hosts: files mdns4_minimal [NOTFOUND=return] resolve
[!UNAVAIL=return] dns myhostname
Thanks. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Could you investigate a bit if this may be related to the new systemd-
reosolvd service? What's /etc/nsswitch.conf say for 'hosts'?
Thanks
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
23 matches
Mail list logo
