DNS problem with mullvad VPN on 18.10












0















My mullvad VPN was working, then I upgraded to 18.10.
Now when I use their UI client, it connects fine, but DNS is not working.
I can ping google.com by IP but not by google.com.



I can resolve it by specifying the interface:



>resolvectl query google.com
google.com: resolve call failed: All attempts to contact name servers or networks failed

>resolvectl -i tun0 query google.com
google.com: 216.58.212.174

-- Information acquired via protocol DNS in 1.1ms.
-- Data is authenticated: no


The man page for resolvectl says this about the -i option:



Note that this option has no effect if system-wide DNS configuration (as configured in /etc/resolv.conf or /etc/systemd/resolve.conf) in place of per-link configuration is used


So is my system using per-link configuration? How do I check that?



Other info:



>ls -ld /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Oct 28 10:10 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

>cat /run/resolvconf/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


Further info as requested:



It is using openvpn 2.4.6-1ubuntu2



Output from systemd-resolve --status (when the vpn is connected):



Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 6 (tun0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 10.9.0.1
DNS Servers: 10.9.0.1

Link 3 (wlp1s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: ~.

Link 2 (eno1)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: ~.


ps auxc | grep dns returns nothing
>ps auxc | grep resolv returns:
systemd+ 557 0.0 0.1 55480 9236 ? Ss Oct28 0:06 systemd-resolve









share|improve this question

























  • whats the output of systemd-resolve --status? What does mullvad VPN use - is it OpenVPN? I think i might be having a similar problem.

    – Maciej Lecki
    Oct 30 '18 at 23:48






  • 1





    Edit your question to include the output of ps auxc | grep -i dns and ps auxc | grep -i resolv. Report back to @heynnema

    – heynnema
    Oct 31 '18 at 14:32
















0















My mullvad VPN was working, then I upgraded to 18.10.
Now when I use their UI client, it connects fine, but DNS is not working.
I can ping google.com by IP but not by google.com.



I can resolve it by specifying the interface:



>resolvectl query google.com
google.com: resolve call failed: All attempts to contact name servers or networks failed

>resolvectl -i tun0 query google.com
google.com: 216.58.212.174

-- Information acquired via protocol DNS in 1.1ms.
-- Data is authenticated: no


The man page for resolvectl says this about the -i option:



Note that this option has no effect if system-wide DNS configuration (as configured in /etc/resolv.conf or /etc/systemd/resolve.conf) in place of per-link configuration is used


So is my system using per-link configuration? How do I check that?



Other info:



>ls -ld /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Oct 28 10:10 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

>cat /run/resolvconf/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


Further info as requested:



It is using openvpn 2.4.6-1ubuntu2



Output from systemd-resolve --status (when the vpn is connected):



Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 6 (tun0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 10.9.0.1
DNS Servers: 10.9.0.1

Link 3 (wlp1s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: ~.

Link 2 (eno1)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: ~.


ps auxc | grep dns returns nothing
>ps auxc | grep resolv returns:
systemd+ 557 0.0 0.1 55480 9236 ? Ss Oct28 0:06 systemd-resolve









share|improve this question

























  • whats the output of systemd-resolve --status? What does mullvad VPN use - is it OpenVPN? I think i might be having a similar problem.

    – Maciej Lecki
    Oct 30 '18 at 23:48






  • 1





    Edit your question to include the output of ps auxc | grep -i dns and ps auxc | grep -i resolv. Report back to @heynnema

    – heynnema
    Oct 31 '18 at 14:32














0












0








0


1






My mullvad VPN was working, then I upgraded to 18.10.
Now when I use their UI client, it connects fine, but DNS is not working.
I can ping google.com by IP but not by google.com.



I can resolve it by specifying the interface:



>resolvectl query google.com
google.com: resolve call failed: All attempts to contact name servers or networks failed

>resolvectl -i tun0 query google.com
google.com: 216.58.212.174

-- Information acquired via protocol DNS in 1.1ms.
-- Data is authenticated: no


The man page for resolvectl says this about the -i option:



Note that this option has no effect if system-wide DNS configuration (as configured in /etc/resolv.conf or /etc/systemd/resolve.conf) in place of per-link configuration is used


So is my system using per-link configuration? How do I check that?



Other info:



>ls -ld /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Oct 28 10:10 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

>cat /run/resolvconf/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


Further info as requested:



It is using openvpn 2.4.6-1ubuntu2



Output from systemd-resolve --status (when the vpn is connected):



Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 6 (tun0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 10.9.0.1
DNS Servers: 10.9.0.1

Link 3 (wlp1s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: ~.

Link 2 (eno1)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: ~.


ps auxc | grep dns returns nothing
>ps auxc | grep resolv returns:
systemd+ 557 0.0 0.1 55480 9236 ? Ss Oct28 0:06 systemd-resolve









share|improve this question
















My mullvad VPN was working, then I upgraded to 18.10.
Now when I use their UI client, it connects fine, but DNS is not working.
I can ping google.com by IP but not by google.com.



I can resolve it by specifying the interface:



>resolvectl query google.com
google.com: resolve call failed: All attempts to contact name servers or networks failed

>resolvectl -i tun0 query google.com
google.com: 216.58.212.174

-- Information acquired via protocol DNS in 1.1ms.
-- Data is authenticated: no


The man page for resolvectl says this about the -i option:



Note that this option has no effect if system-wide DNS configuration (as configured in /etc/resolv.conf or /etc/systemd/resolve.conf) in place of per-link configuration is used


So is my system using per-link configuration? How do I check that?



Other info:



>ls -ld /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Oct 28 10:10 /etc/resolv.conf -> ../run/resolvconf/resolv.conf

>cat /run/resolvconf/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


Further info as requested:



It is using openvpn 2.4.6-1ubuntu2



Output from systemd-resolve --status (when the vpn is connected):



Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 6 (tun0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 10.9.0.1
DNS Servers: 10.9.0.1

Link 3 (wlp1s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: ~.

Link 2 (eno1)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: ~.


ps auxc | grep dns returns nothing
>ps auxc | grep resolv returns:
systemd+ 557 0.0 0.1 55480 9236 ? Ss Oct28 0:06 systemd-resolve






dns vpn






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 2 '18 at 2:43







user3014416

















asked Oct 28 '18 at 15:26









user3014416user3014416

1063




1063













  • whats the output of systemd-resolve --status? What does mullvad VPN use - is it OpenVPN? I think i might be having a similar problem.

    – Maciej Lecki
    Oct 30 '18 at 23:48






  • 1





    Edit your question to include the output of ps auxc | grep -i dns and ps auxc | grep -i resolv. Report back to @heynnema

    – heynnema
    Oct 31 '18 at 14:32



















  • whats the output of systemd-resolve --status? What does mullvad VPN use - is it OpenVPN? I think i might be having a similar problem.

    – Maciej Lecki
    Oct 30 '18 at 23:48






  • 1





    Edit your question to include the output of ps auxc | grep -i dns and ps auxc | grep -i resolv. Report back to @heynnema

    – heynnema
    Oct 31 '18 at 14:32

















whats the output of systemd-resolve --status? What does mullvad VPN use - is it OpenVPN? I think i might be having a similar problem.

– Maciej Lecki
Oct 30 '18 at 23:48





whats the output of systemd-resolve --status? What does mullvad VPN use - is it OpenVPN? I think i might be having a similar problem.

– Maciej Lecki
Oct 30 '18 at 23:48




1




1





Edit your question to include the output of ps auxc | grep -i dns and ps auxc | grep -i resolv. Report back to @heynnema

– heynnema
Oct 31 '18 at 14:32





Edit your question to include the output of ps auxc | grep -i dns and ps auxc | grep -i resolv. Report back to @heynnema

– heynnema
Oct 31 '18 at 14:32










2 Answers
2






active

oldest

votes


















0














I emailed mullvad support and they suggested that I just use openvpn, i.e. same response as Coffee_Mug in:
Mullvad vpn won't connect on ubuntu 18.04



On one computer, I used the old mulvad client via "env MULLVAD_USE_GTK3=yes mullvad", but on the other I got the same error as amicose in
Mullvad VPN Client won't start on 18.04



For that second computer, I gave up trying to figure out why it wouldn't work and just set up openvpn to connect to one server.






share|improve this answer































    0














    Version 2018.6 of the Mullvad app works fine






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1088031%2fdns-problem-with-mullvad-vpn-on-18-10%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      I emailed mullvad support and they suggested that I just use openvpn, i.e. same response as Coffee_Mug in:
      Mullvad vpn won't connect on ubuntu 18.04



      On one computer, I used the old mulvad client via "env MULLVAD_USE_GTK3=yes mullvad", but on the other I got the same error as amicose in
      Mullvad VPN Client won't start on 18.04



      For that second computer, I gave up trying to figure out why it wouldn't work and just set up openvpn to connect to one server.






      share|improve this answer




























        0














        I emailed mullvad support and they suggested that I just use openvpn, i.e. same response as Coffee_Mug in:
        Mullvad vpn won't connect on ubuntu 18.04



        On one computer, I used the old mulvad client via "env MULLVAD_USE_GTK3=yes mullvad", but on the other I got the same error as amicose in
        Mullvad VPN Client won't start on 18.04



        For that second computer, I gave up trying to figure out why it wouldn't work and just set up openvpn to connect to one server.






        share|improve this answer


























          0












          0








          0







          I emailed mullvad support and they suggested that I just use openvpn, i.e. same response as Coffee_Mug in:
          Mullvad vpn won't connect on ubuntu 18.04



          On one computer, I used the old mulvad client via "env MULLVAD_USE_GTK3=yes mullvad", but on the other I got the same error as amicose in
          Mullvad VPN Client won't start on 18.04



          For that second computer, I gave up trying to figure out why it wouldn't work and just set up openvpn to connect to one server.






          share|improve this answer













          I emailed mullvad support and they suggested that I just use openvpn, i.e. same response as Coffee_Mug in:
          Mullvad vpn won't connect on ubuntu 18.04



          On one computer, I used the old mulvad client via "env MULLVAD_USE_GTK3=yes mullvad", but on the other I got the same error as amicose in
          Mullvad VPN Client won't start on 18.04



          For that second computer, I gave up trying to figure out why it wouldn't work and just set up openvpn to connect to one server.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 11 '18 at 17:16









          user3014416user3014416

          1063




          1063

























              0














              Version 2018.6 of the Mullvad app works fine






              share|improve this answer




























                0














                Version 2018.6 of the Mullvad app works fine






                share|improve this answer


























                  0












                  0








                  0







                  Version 2018.6 of the Mullvad app works fine






                  share|improve this answer













                  Version 2018.6 of the Mullvad app works fine







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 26 at 20:13









                  user3014416user3014416

                  1063




                  1063






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1088031%2fdns-problem-with-mullvad-vpn-on-18-10%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      How to make a Squid Proxy server?

                      Is this a new Fibonacci Identity?

                      Touch on Surface Book