Issue with sys-net DNS

Hello! I’m a new user to Qubes OS and the forums, I’ve just yesterday installed it, however I’m experiencing an issue with the DNS outside of the sys-net qube, I tested inside of the sys-net qube‘s terminal pinging www.google.com and 8.8.8.8, they both worked, but in any other qube, pinging 8.8.8.8 works but www.google.com does not.

So far to fix this issue I’ve tried a few solutions I found online;

  1. shutting sys-net and sys-firewall down, then starting sys-net then sys-firewall again
  2. adding 8.8.8.8 to networkmanager‘s settings
  3. running /usr/lib/qubes/qubes-setup-dnat-to-ns then restarting both the sys-net and sys-firewall Qubes
  4. simply rebooting my system

Does anyone here know how to help at this point? It was working before, and I don’t remember what it is I did to cause this…

Hi ainselu - and welcome to the Qubes Forum :slight_smile:

When you can only ping www.google.com from sys-net, how does the output from the command look? - does it have IPv4 or IPv6 addresses?

:slight_smile:

1 Like

Hello, thank you! It only has IPv6 addresses when I ping google inside of sys-net; it returns:
„PING www.google,com(rr-in-f105.le100,net (2607:f8b0:4023:1002)) 56 data bytes“
then „64 bytes from rr-in-f105.le100,net (2607:f8b0:4023:1002): icmp_seq=1 ttl=58 time=30.8 ms“
and so on whenever packets are received

Hi Ainselu

Right - and when you try in the Qubes that has issues, DNS still point to the IPv6 address … but the Qube only have IPv4?

[Edit: If you want IPv6, you can look at:

]

:slight_smile:

1 Like

Hi Chris! I‘m not sure, when I try to ping google in a qube outside of sys-net it does nothing for a while before giving me „Temporary failure in name resolution“

Hmm - that was not what I expected – time to look at the drawing board again … :-/

:slight_smile:

1 Like

Hmm, well, I’ve found that when I ping google outside of sys-net, it reaches sys-firewall, but it doesn’t seem to reach sys-net (according to tcpdump), and when I ping google in sys-firewall, it reaches sys-net but it doesn’t appear to send back a valid response, if this helps, I still haven’t been able to fix this though :frowning: