Actually, one thing I just remembered. resolved never actually writes to /etc/resolv.conf, if I remember correctly. It only writes to a .conf in /run, and /etc/resolv.conf is just a symlink to the latter.
So you could just have a static /etc/resolv.conf with 127.0.0.1 in it, and tell your cache to look in /run/systemd/resolv.conf for the upstream servers' addresses. I'm sure at least dnsmasq has that ability. -- Mantas Mikulėnas <graw...@gmail.com> // sent from phone On Jun 17, 2014 2:14 PM, "Runiq" <ru...@archlinux.us> wrote: > Hello all, > > I'm using systemd 213 on Arch Linux, and systemd-networkd/resolved with > DHCP to connect to the internet. I'm also running a caching DNS server on > 127.0.0.1. > > I'd like to make this caching server the first DNS server in the list, but > I'd also like to use the nameservers discovered by systemd-resolved. Using > a static resolv.conf isn't really possible, because I connect to networks > with different DNS settings. > > I know I can set *fallback* DNS servers in /etc/systemd/resolved.conf, but > is there a way with systemd-networkd to prepend my local DNS server to > those discovered by DHCP? > > I've asked this question on superuser.com [1] but didn't get a > satisfactory reply. > > Thanks, > Patrice > > [1] http://superuser.com/q/767827/260249 > > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > >
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel