It seems from another another thread and testing on my VM that if OMV uses DHCP and the DNS is changed/added to the DHCP setting in Network -> Interfaces the change does not take effect in /etc/resolv.conf and OMV continues to DNS issued by the DHCP server.
OMV5 DNS change
-
- OMV 5.x
- geaves
-
-
the change does not take effect in /etc/resolv.conf and OMV continues to DNS issued by the DHCP server.
Depends on what is in /etc/resolv.conf. If it is 127.0.0.53, then it is using systemd-resolved (local dns caching) which should be using the dns server you set.
-
Thanks for the reply, my resolv.conf points to the DNS issued by my router, which in my case is my Pi-Hole IP, this is on my VM which shouldn't make any difference.
-
my resolv.conf points to the DNS issued by my router, which in my case is my Pi-Hole IP, this is on my VM which shouldn't make any difference.
I don't know what it is set to versus what it should be set to. Also, what is the output of: ls -al /etc/resolv.conf
-
When I first up the VM I go down each item and make relevant changes or ensure that options are set accordingly, then do updates, so I entered 1.1.1.1 to the DNS entry of the DHCP address under Network -> Interfaces, then save and apply, except the DNS entry does not take effect if the resolv.conf is correct.
-
It isn't changing because /etc/resolv.conf is not a symlink to /run/systemd/resolve/resolv.conf
Fix it with:
sudo rm /etc/resolv.conf && sudo ln -s /run/systemd/resolve/resolv.conf /etc/
-
Fix it with:
Ok that works, now it shows 2 nameservers in resolv.conf, which I would assume one is primary and the other secondary.
As this was the iso install was there a change made that has not effectively applied to my VM
-
was there a change made that has not effectively applied to my VM
Maybe you have resolvconf installed? dpkg -l | grep resolvconf
-
Maybe you have resolvconf installed
No, returned nothing.
-
Not sure. Was the system upgraded?
-
Not sure. Was the system upgraded?
No clean install, as it's working and there is another thread where the resolv.conf was pointing to their router. TBH I was expecting the DNS to change after adding a public in Network -> Interfaces, but this might be useful in the other thread.
-
OMV ensures that the file is a symlink when the package is installed, see https://github.com/openmediava…up/resolvconf/default.sls and https://github.com/openmediava…n/openmediavault.postinst. This can be done manually via omv-salt stage run setup.
-
Interesting. Just checked on my system. I had upgraded from OMV 4 to 5. /etc/resolv.conf was not symlinked. There is no resolve directory within /run/systemd. I ran the omv-salt command, but no change. /etc/resolv.conf just contains my (standard) nameserver entry directly.
-
Interesting. Just checked on my system. I had upgraded from OMV 4 to 5. /etc/resolv.conf was not symlinked.
Have you installed all available OMV updates yet?
-
Are all systemd-network and systemd-resolved units running?
-
This can be done manually via omv-salt stage run setup
Well that changed something on my system, as the resolv.conf now places the public dns first and the pi-hole dns second (issued by DHCP)
-
gderf Yes, all updates have been installed.
votdev I'm not exactly sure how to check that, but got the following:
Coderoot@MyRS:/etc/systemd# systemctl is-active network inactive root@MyRS:/etc/systemd# systemctl is-active resolvd inactive
I do experience regular connection issues across docker containers since some time though. They coincide with the following syslog entries.
CodeSep 11 00:09:39 MyRS rsyncd[1963]: forward name lookup for unifi.local failed: Name or service not known Sep 11 00:09:39 MyRS rsyncd[1963]: connect from UNKNOWN (192.168.1.1) Sep 11 00:09:44 MyRS smbd[1966]: [2020/09/11 00:09:44.986037, 0] ../source3/smbd/process.c:335(read_packet_remainder) Sep 11 00:09:44 MyRS smbd[1966]: read_fd_with_timeout failed for client 192.168.1.1 read error = NT_STATUS_END_OF_FILE.
Might not be related though and I don't want to hijack the thread...
-
I believed I've figured out the rsyncd / smbd problem. Permissions for the rsync target were not set correctly. Not related. The first part of the question remains though. Any advice appreciated...
-
Hi I was looking to solve a similar problem and I followed the indication above but now I cannot still update the OMV and the '/etc/resolv.conf' is
missing.
Could you please help me
Thanks
-
the '/etc/resolv.conf' is
missing.
ln -s /run/systemd/resolve/resolv.conf /etc/
to recreate the missing symlink
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!