Temporary failure in name resolution in app VM's

User Support
1

I looked I have gotten as far as I can. I know people have had this issue before, but my situation is different from other forum posts. When I run
"ping google.com "
In sys-net, I would get
“temporary failure in name resolution”
After some troubleshooting, I could ping in sys-net by opening ports 43 and 53 via qvm-firewall. Now I can ping in sys-net, but I can’t ping in sys-firewall, or any app VM. Even in an appVM that connects directly to sys-net.

I have tried systemctl stop systemd-resolved, and that returns
“systemd-resolved” not running.

Debian is my default app template, and the internet was working less than a week ago.
There was a debian update that came through to my system.

I have checked, and I have two namespaces.

2

Hi Almyu - and welcome to the forum! :slight_smile:

Can you elaborate on

“I can ping in sys-net”

?

A problem with

ping google.com

is both ping (ICMP traffic) and DNS (resolution of ‘google.com’) - where as a problem with

ping 8.8.8.8

or

host dns.google

could narrow the issue down to just one of the two …

:slight_smile:

3

Hi Chris! Thanks for the welcome

I believe the problem is with the DNS resolution portion of ping. Using
ping google.com
In sys-net will return the expected ping output with all the data.
but using
ping google.com in any appVM will return
temporary failure in name resolution.

Something I just noticed, using ping at any IP address, 8.8.8.8, a local computer, and even my router will return the expected ping output, but with
destination net unreachable
In the data field. This confused me even more, because using a domain name works as expected.