OMV not resolving hostnames and some repositories

MrFloppyDisc · 22. November 2020

Hi everyone, when I'm trying to update my OMV 5 install or install something with apt it gives me this output:

Code

W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease  Could not resolve 'deb.debian.org'
W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease  Could not resolve 'security.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease  Could not resolve 'deb.debian.org'
W: Failed to fetch https://deb.debian.org/debian/dists/buster-backports/InRelease  Could not resolve 'deb.debian.org'
W: Failed to fetch https://packages.openmediavault.org/public/dists/usul/InRelease  Could not resolve 'packages.openmediavault.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

I tried changing the DNS I had (89.2.0.1) to 8.8.8.8 but it didn't help. Also the auto configurator takes a long time before saying something like "Ressource busy or unavailable". And I had to put my router's settings (like the IP address, DNS and stuff like this (for example instead of 192.168.0.1 for the gateway I had to put something else) because otherwise it wouldn't work.

Help is appreciated

macom · 22. November 2020

Please post the output of

cat /etc/resolv.conf

ls -al /etc/resolv.conf

systemctl status systemd-resolved.service

MrFloppyDisc · 22. November 2020

Here:

Code

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 8.8.8.8

Alles anzeigen

Code

lrwxrwxrwx 1 root root 32 Nov 21 22:35 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

Code

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 8.8.8.8
root@T180-250GO:~# ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 32 Nov 21 22:35 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf
root@T180-250GO:~# systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/systemd-resolved.service.d
           └─resolvconf.conf
   Active: active (running) since Sun 2020-11-22 13:40:01 CET; 24min ago
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 397 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 1124)
   Memory: 4.3M
   CGroup: /system.slice/systemd-resolved.service
           └─397 /lib/systemd/systemd-resolved

Nov 22 13:40:00 T180-250GO.local systemd[1]: Starting Network Name Resolution...
Nov 22 13:40:01 T180-250GO.local systemd-resolved[397]: Positive Trust Anchors:
Nov 22 13:40:01 T180-250GO.local systemd-resolved[397]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Nov 22 13:40:01 T180-250GO.local systemd-resolved[397]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Nov 22 13:40:01 T180-250GO.local systemd-resolved[397]: Negative trust anchors: 10.in-addr.arpa 16.172.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
Nov 22 13:40:01 T180-250GO.local systemd-resolved[397]: Using system hostname 'T180-250GO.local'.
Nov 22 13:40:01 T180-250GO.local systemd[1]: Started Network Name Resolution.

Alles anzeigen

macom · 22. November 2020

Looks all correct. Are you able to ping domains?

ping -c 4 google.com

and

ping -c 4 8.8.8.8

MrFloppyDisc · 22. November 2020

Well, it gives me this (also I changed the DNS back to 89.2.0.1)

Code

root@T180-250GO:~# ping -c 4 8.8.8.8
connect: Network is unreachable
root@T180-250GO:~# ping -c 4 google.com
ping: google.com: Name or service not known

macom · 22. November 2020

You have an issue with your network connection, not only DNS.

Check your cable.

Check if other devices have internet connection.

MrFloppyDisc · 22. November 2020

My cable is alright, it works really well with other devices, and other devices work really well with my network, so I don't see why it wouldn't work (also my NAS is connected because I can access the web config page)

macom · 22. November 2020

Try omv-firstaid to configure your network interface. Use dhcp, not static IP for the moment.

MrFloppyDisc · 22. November 2020

Somehow, it worked and now everything seems to be working as it should. Well thanks for your help.

rtkegger · 17. März 2023

Over 2 years later this is still good advice. Thanks

OMV not resolving hostnames and some repositories

MrFloppyDisc 22. November 2020

macom 30. Januar 2021

Jetzt mitmachen!

Tags