DNS issues

I'm running OMV 6.4.6 on baremetal. Since the last upgrade I noticed that the system doesn't resolve my local DNS records anymore.

The system is set up with DHCP and it receives two nameservers: 10.11.12.77, 10.11.12.1 - first one is the Pi-hole I run, second one is the router which forwards the requests to my ISP's DNS. I have set up some local hosts in the Pi-hole and it worked like a charm until a week ago. Also, I notice this happens only on the OMV machine.

Checking /etc/resolv.conf, it points correctly to /run/systemd/resolve/stub-resolv.conf, but running resolvectl I see it point to the router's IP address as default nameserver:

# resolvectl
Global
       Protocols: +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink

Link 2 (enp3s0)
Current Scopes: DNS LLMNR/IPv4
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 10.11.12.1
DNS Servers: 10.11.12.77 10.11.12.1

What can I do to have .77 as default DNS always?

Quote from votdev

The decision is done by systemd-resolved as far as I have found out with Google. The fastest DNS server wins. I think you need to configure your DHCP server to only submit the IP address of interest.

As a workaround go the OMV network interface config page in the UI and enter 10.11.12.77 in the DNS server field. This way your manuall config will overrule DHCP.

Thanks. I thought of that too.. I'll play with some settings to see what helps better. I prefer to keep the DHCP server as it is, because sometimes the Pi-hole (very rarely) goes down and the second IP helps.

PS: also, my pi-hole is in fact a docker container on OMV itself, so I find it funny that the connection to it would be slower than to the router.

Quote from raulfg3

perhaps can help you:

https://wiki.omv-extras.org/do…_the_same_lan_as_the_host

Thread

docker composer - networks

Hi all,

I am trying to migrate from Portrainer to Composer, and I have a question about the network configuration.

Prior, in Portainer, this was my config:
(Code, 15 lines)


... and I was using 192.168.1.x as the network in all my containers. Each with a different IP.

Now I'm trying to use this config, creating a file to each container:
(Code, 18 lines)


Only with this container, all was fine. But when I try to add another container with same config (only changing ipv4_address and ip_range) it says:…

Jubri

Jul 1st 2023

This looks really great. I tried it and I was able to ping the host from the container, but not the other way around. I'll check this again this weekend, maybe I've overlooked something.

Thanks for pointing me to this!