You are not logged in.
Hi all,
Up until now, I used systemd-networkd to handle the network of my workstation without systemd-resolved and manually put the nameservers into /etc/resolv.conf.
These are
1) our VPN server for intranet domain resolution.
2) our office router for internet domain resolution.
This worked fine. But, interestingly, reversing the order of the DNS servers will cause the intranet domains not to be resolved any longer.
I now wanted to let systemd-resolved to handle the DNS resolution for me.
But I cannot get systemd-resolved to use the fallback DNS server for our intranet.
/etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details
[Resolve]
DNS=<office_router>
FallbackDNS=<vpn_server>
Domains=<intranet_domain_with_dot_at_the_end>
#LLMNR=yes
#MulticastDNS=yes
#DNSSEC=no
#Cache=yes
#DNSStubListener=udp
My questions are:
How do I get systemd-resolved to resolve all intranet domains via our VPN server and all other domains via our office router?
I'd also be interested if someone could explain to me, why the order of the name servers in /etc/resolve.conf makes such a big difference.
Solved (kinda)
systemd-resolved does not seem to be the right software for my requirements.
At least not alone.
I set up dnsmasq on my workstation to locally serve the respective DNS resolution and configured systemd-resolved to just delegate to it.
Last edited by schard (2018-09-24 13:57:59)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline