Upgrade to openmediavault 5.1.3-1 breaks DNS reolution

gderf · 22. Dezember 2019

Perhaps my installation has quirks that either cause this problem or contribute to it.

What happened previously from time to time was that the file /etc/resolv.conf would be deleted somehow, breaking name resolution. I keep a backup copy of that file and restoring it is easy.

When I updated to openmediavault 5.1.3-1 this morning, resolution broke again so I tried to restore the /etc/resolv.conf file. However, this did not work because /etc/resolv.conf does exist but not as a file. It's now symbolic link to /run/systemd/resolve/resolv.conf. I believe this linking is more in line with how Debian does name resolution on Buster. The problem is that the directory /run/systemd/resolve does not exist. I created it and placed a copy of the file resolv.conf in it and resolution now works.

ryecoaaron · 22. Dezember 2019

systemd-resolved maintains that file. There was a probably an update that caused it to re-config. OMV should probably disable it or configure it.

gderf · 22. Dezember 2019

It was fine until I upgraded to openmediavault 5.1.3-1 because the date and time on the new symbolic link agreed with the time of the upgrade.

I immediately had my mailbox flood with messages from Watchtower indicating resolution was not working.

ryecoaaron · 22. Dezember 2019

I have a few systems running 5.1.3-1 and /etc/resolv.conf is still symlink'd to the same place. If I have some time, I will try to replicate this.

donh · 22. Dezember 2019

There is now a 5.2.0-1 update? Might break it again. LOL

gderf · 22. Dezember 2019

Zitat von ryecoaaron

systemd-resolved maintains that file. There was a probably an update that caused it to re-config. OMV should probably disable it or configure it.

If systemd-resolved is a service, I don't have it running here.

gderf · 22. Dezember 2019

Zitat von donh

There is now a 5.2.0-1 update? Might break it again. LOL

Not seeing that udpate here.

ryecoaaron · 22. Dezember 2019

Zitat von donh

There is now a 5.2.0-1 update? Might break it again.

Just upgraded two systems. /etc/resolv.conf is still being maintained by systemd-resolved and is correct.

ryecoaaron · 22. Dezember 2019

Zitat von gderf

If systemd-resolved is a service, I don't have it running here.

If you don't have systemd-resolved running (it is running on my system), then you want the resolvconf package installed.

edit - I just looked at the code and systemd-resolved enabled and running is the desired state for OMV. Unfortunately, this code only runs once. @votdev maybe salt should be setting this when network changes are made? If some don't like that, maybe a system variable to not use systemd-resolved?

gderf · 22. Dezember 2019

resolvconf was installed but not running and not in the services list so I reinstalled it. It's running now.

I one adds DNS servers to an interface using OMV's Network page, where are they written to?

ryecoaaron · 22. Dezember 2019

Zitat von gderf

I one adds DNS servers to an interface using OMV's Network page, where are they written to?

They should be in /etc/systemd/network/10-openmediavault-ens192.network if specified in the web interface. ens192 will change to whatever your nic is named. From there, systemd-resolved (and probably resolvconf) will configure /etc/resolv.conf (or the file it is symlink'd to).

Jetzt mitmachen!