*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
can not find local pc's since Ubuntu 22.0.4 to 24.04
sudo nano /etc/nsswitch.conf
sudo nano /etc/mdns.allow
aio@aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
aio@aio:~$ ls -l /etc/systemd/system/systemd-resolved.service
ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file
or directory
aio@aio:~$ sudo systemctl unmask systemd-resolved
aio@aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
aio@aio:~$ sudo dpkg-reconfigure resolvconf
dpkg-query: package 'resolvconf' is not installed and no information is
available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolvconf is not installed
aio@aio:~$ sudo apt install systemd-resolved
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
systemd-resolved is already the newest version (255.4-1ubuntu8.1).
systemd-resolved set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
aio@aio:~$ sudo dpkg-reconfigure resolvconf
dpkg-query: package 'resolvconf' is not installed and no information is
available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolvconf is not installed
aio@aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
aio@aio:~$ sudo apt install systemd-resolved
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
systemd-resolved is already the newest version (255.4-1ubuntu8.1).
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
aio@aio:~$ sudo apt install --reinstall systemd-resolved
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 33 not upgraded.
Need to get 0 B/296 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 838554 files and directories currently installed.)
Preparing to unpack .../systemd-resolved_255.4-1ubuntu8.1_amd64.deb ...
Unpacking systemd-resolved (255.4-1ubuntu8.1) over (255.4-1ubuntu8.1) ...
Setting up systemd-resolved (255.4-1ubuntu8.1) ...
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148.
Processing triggers for dbus (1.14.10-4ubuntu4) ...
Processing triggers for man-db (2.12.0-4build2) ...
Config is in use.
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...
Running kernel seems to be up-to-date.
The processor microcode seems to be up-to-date.
Restarting services...
systemctl restart systemd-resolved.service
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
No containers need to be restarted.
User sessions running outdated binaries:
aio @ user manager service:
chrome[174774,174791,174792,174794,891445,891462,891463,891465],
gnome-session-b[169989], gnome-shell[170020],
surfshark[170400,170719,170720,170767], systemd[169581]
No VM guests are running outdated hypervisor (qemu) binaries on this host.
aio@aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
aio@aio:~$ service systemd-resolved start
Failed to start systemd-resolved.service: Unit var-tmp.mount is masked.
aio@aio:~$ ls -l /etc/systemd/system/systemd-resolved.service
ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file
or directory
aio@aio:~$ sudo ls -l /etc/systemd/system/systemd-resolved.service
ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file
or directory
aio@aio:~$ sudo systemctl daemon-reload
aio@aio:~$ sudo systemctl start systemd-resolved
Failed to start systemd-resolved.service: Unit var-tmp.mount is masked.
aio@aio:~$ sudo systemctl enable systemd-resolved
aio@aio:~$ sudo systemctl start systemd-resolved
Failed to start systemd-resolved.service: Unit var-tmp.mount is masked.
aio@aio:~$ sudo dpkg-reconfigure resolvconf
dpkg-query: package 'resolvconf' is not installed and no information is
available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolvconf is not installed
aio@aio:~$ sudo dpkg-reconfigure resolved
dpkg-query: package 'resolved' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolved is not installed
aio@aio:~$ sudo dpkg-reconfigure resolve
dpkg-query: package 'resolve' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolve is not installed
aio@aio:~$ ping aio
PING aio (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.061 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.040 ms
^C
--- aio ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1030ms
rtt min/avg/max/mdev = 0.040/0.050/0.061/0.010 ms
aio@aio:~$ ping laptop2
ping: laptop2: Name or service not known
aio@aio:~$ sudo systemctl unmask systemd-networkd.service
aio@aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055012
Title:
When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
