DNS resolution issue

delpiero3 · 28. Dezember 2022

Hi everyone,

hope you are all doing good ?

Recently, i noticed that i wasn't receiving anymore emails from my OMV installations with updates.

After connecting it through SSH, i noticed that i couldn't ping http://www.google.com. I started to check resolved service and avahi, both seems to be up and running :

Code

root@media:~# systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-12-27 11:01:25 CET; 24h ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 2849650 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 38452)
     Memory: 5.4M
        CPU: 2.567s
     CGroup: /system.slice/systemd-resolved.service
             └─2849650 /lib/systemd/systemd-resolved

Dec 27 11:01:24 media systemd[1]: Starting Network Name Resolution...
Dec 27 11:01:24 media systemd-resolved[2849650]: Positive Trust Anchors:
Dec 27 11:01:24 media systemd-resolved[2849650]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Dec 27 11:01:24 media systemd-resolved[2849650]: 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.172.in-addr.arpa 24.172.in-add
r.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.1
72.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Dec 27 11:01:25 media systemd-resolved[2849650]: Using system hostname 'media'.
Dec 27 11:01:25 media systemd[1]: Started Network Name Resolution.
root@media:~# ping www.google.be 
ping: www.google.be: Name or service not known
root@media:~# systemctl status avahi-daemon.service 
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-12-19 06:12:50 CET; 1 weeks 2 days ago
TriggeredBy: ● avahi-daemon.socket
   Main PID: 21043 (avahi-daemon)
     Status: "avahi-daemon 0.8 starting up."
      Tasks: 2 (limit: 38452)
     Memory: 1.6M
        CPU: 7min 48.290s
     CGroup: /system.slice/avahi-daemon.service
             ├─21043 avahi-daemon: running [media.local]
             └─21044 avahi-daemon: chroot helper

Dec 19 06:19:40 media avahi-daemon[21043]: Leaving mDNS multicast group on interface ens18.IPv6 with address fe80::182a:8fff:fee3:c
0e1.
Dec 19 06:19:40 media avahi-daemon[21043]: Joining mDNS multicast group on interface ens18.IPv6 with address 2a02:2788:8f4:1a1:182a
:8fff:fee3:c0e1.
Dec 19 06:19:40 media avahi-daemon[21043]: Registering new address record for 2a02:2788:8f4:1a1:182a:8fff:fee3:c0e1 on ens18.*.
Dec 19 06:19:40 media avahi-daemon[21043]: Withdrawing address record for fe80::182a:8fff:fee3:c0e1 on ens18.
Dec 19 13:37:32 media avahi-daemon[21043]: Files changed, reloading.
Dec 19 13:37:43 media avahi-daemon[21043]: Files changed, reloading.
Dec 19 13:37:58 media avahi-daemon[21043]: Files changed, reloading.
Dec 19 13:38:50 media avahi-daemon[21043]: Files changed, reloading.
Dec 27 10:29:48 media avahi-daemon[21043]: Files changed, reloading.
Dec 27 10:30:17 media avahi-daemon[21043]: Files changed, reloading.

Alles anzeigen

I tried to reset my network configuration using omv-firstaid, using netplan, nothing is working. When i do "cat /etc/resolv.conf", all looks good as well :

Code

root@media:~# cat /etc/resolv.conf 
# 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 should typically 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 192.168.200.200
nameserver 192.168.200.200
nameserver 2a02:2788:8f4:1a1:1::223

Alles anzeigen

I am not sure what am i missing here ?

last note, i noticed that SMB sharing through hostname doesn't work either.

I am using a bunch of docker, that seems to work without any issue, all docker running on that OMV instance can resolve domains.

Thanks for the help.

cheers

BernH · 28. Dezember 2022

Are you using a static IP or a dynamic IP on OMV.

Dynamic relies on your DHCP server to send all the configuration to the NIC. Static has to be entered manually.

If you are using static, you have to specify the IP, gateway and DNS servers yourself in the OMV interfaces section.

If you are on dynamic, reboot your router and then your server. I have seen them sometimes get a bit confused after months or sometimes years of being on, and a reboot fixed any errors after manifesting in the lease tables or routing tables.

delpiero3 · 29. Dezember 2022

Already tried both, doesn't change anything. Tried different DNS, like 1.1.1.1, doesn't change anything. My router is rebooted once a month, it is OPNSense, and i apply updates.

Tried it one more time today, and suddenly, all works, in DHCP or static. Don't know what happened, spend almost a day on this one.

Thanks for asking me this, so that i could try one more time and finally got the issue fixed.

Cheers.

BernH · 29. Dezember 2022

It sounds like you may have had some problems with opnsense to me. Since it is opnsense, it is running on some kind of computer.

Just a little tip from my 30 years as an electronics technician and a computer repair technician.

Sometimes a reboot isn’t enough.

Sometimes a full power cycle is required.

Sometime you even need to drain any residual voltages from capacitors on the motherboard for all the chips and Ram to do a full reset. You can try doing this forcefully by shutting down, removing power and pressing and holding the power button for 20 seconds or so, then reapply power and start up.

Sometimes even that isn’t enough if it doesn’t drain all the capacitors and you need to shut down, remove power and wait 20-30 minutes. If it comes to this I will still do the power button press and hold, but wait that 20-30 minutes before reapplying power.

Computers are great when they work, but when they get cranky they can stop making sense.

Wolf2000 · 29. Dezember 2022

BernH

I think the router had a problem

Server, Nas, printer should e.g. 192.168.200.80-120 Have.

And he maybe has ip6?

BernH · 29. Dezember 2022

Zitat von Wolf2000

BernH
I think the router had a problem
Server, Nas, printer should e.g. 192.168.200.80-120 Have.
And he maybe has ip6?

That is what I said, opnsense is his router/dhcp server/gateway.

Since there is no real need for ipv6 on a home LAN, unless you have more computers than there are on the internet, I don't use it, but it should still issue addresses and route.

Although both ipv4 and ipv6 can be used simutaneously, I'm sure it gives more chance for a router to get its routing tables messed up.

DNS resolution issue

delpiero3 29. Dezember 2022

delpiero3 29. Dezember 2022

Jetzt mitmachen!

Ähnliche Themen

OMV-EXTRAS 6.x

openmediavault-onedrive 6.1.0-1 - omv-onedrive-auth command not working

the setting of static ip is now work