OMV5 DNS change

1st Official Post
    • Official Post

    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.

    Raid is not a backup! Would you go skydiving without a parachute?


    OMV 8x amd64 running on an HP N54L Microserver

    • Official Post
    Quote from 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.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from geaves

    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

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Code
    ls -al /etc/resolv.conf
-rw-r--r-- 1 root root 48 Aug 18 15:21 /etc/resolv.conf
    Code
    cat /etc/resolv.conf
domain home
search home
nameserver 192.168.1.43

    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.

    • Official Post

    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/

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from geaves

    was there a change made that has not effectively applied to my VM

    Maybe you have resolvconf installed? dpkg -l | grep resolvconf

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    Not sure. Was the system upgraded?

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from ryecoaaron

    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.

    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.

    Quote from m4tt0

    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?

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    gderf Yes, all updates have been installed.

    votdev I'm not exactly sure how to check that, but got the following:

    Code
    root@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.

    Code
    Sep 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

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login