If that is the case your configuration doesn't make sense as you have no control in which situation which DNS server is chosen.
The fact is that it works, at least in my case, and I have never read a complaint on the forum about this configuration. IP addresses are resolved from my DNS server when they exist, as I already said.
From what I can see, this has been done this way for at least 9 years. So we can already consider it as "OMV Historical Memory" or "Traditions settled in time" 
If you want to know how DNS is resolved by systemd-resolved, please check the docs. But i remember that i read that the DNS servers are used according to their order.
Also note that systemd-resolved is used in stub-mode.
To be fair, I was up until midnight fixing problems regarding omv updates and dhcp/dns resolution.
In one case, I do have blocky running in docker and so need port 53 and had disabled systemd-resolved rather than disabling as per this link: https://github.com/pi-hole/doc…lling-on-ubuntu-or-fedora
but even after that I have weird things happening with DHCP and it wouldn't get an address and I ended up putting a static IP on them.
I don't know if that helps, but you're not alone.
but even after that I have weird things happening with DHCP and it wouldn't get an address and I ended up putting a static IP on them.
That matches the link matdb posted in post #8
As long as these upstream issues are not resolved, strange behavior will continue. https://github.com/systemd/systemd/issues/27854 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036949
For "local DNS" I use my LAN's DHCP server.
Even when the client is statically addressed, setting a permanent "DHCP lease" for the same IP address groups the client's MAC address, Hostname and IP address together. Thereafter, local name lookups are resolved by the DHCP server.
For "external DNS" lookups I'm using my own recursive DNS server, -> Unbound. For cached entries, there's nothing faster. Some years ago, I set up an old R-PI with Unbound and Pi-hole as a DNS appliance. All references to a "DNS server" are given the R-PI's IP address. This includes the LAN's router, statically set DNS entries on clients, etc.
I found a -> How-To that approximates what I did. (However, I used DietPI and I "hard" disabled IPv6.)
After scanning the How-To, the one thing they didn't cover is how to update Unbound's list of root servers. It's not difficult.
On the CLI as root:
service unbound stop && wget -O root.hints https://www.internic.net/domain/named.root
mv root.hints /var/lib/unbound/ && service unbound start
The update is only needed once in a year or two. The list of roots servers rarely changes.
Yesterday i did some more research on how systemd-resolved works. There were some design decisions related to single-label hostnames. The problem is that if the DHCP server of your router does not deliver a domainname, resolving such single-label hostnames will not be successful. So if this does not work, check the DHCP server if it acts correct.
If there are still problems with resolving single-labels, there is a workaround by adding
ResolveUnicastSingleLabel=yesto /etc/systemd/resolved.conf.d/foo-bar-baz.conf and restart systemd-resolved. But this is a security problem with public DNS servers; so use this only if your DNS server is your own.
References:
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!