On Tue, 17.06.14 13:14, 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
On 17.06.2014 14:43:25, Mantas Mikulėnas wrote:
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
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
I am not sure about the part where you talk about different networks' DNS
settings.
I mean, as long as the first-listed server responds – and localhost always
responds – then the fallback servers won't be used at all.
So what's the point of having both 127.0.0.1 and external servers listed
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
On Tue, Jun 17, 2014 at 4:33 AM, Mantas Mikulėnas graw...@gmail.com wrote:
I mean, as long as the first-listed server responds – and localhost always
responds – then the fallback servers won't be used at all.
Localhost can be subject to two types of failure:
* The local daemon being down.
*
