4 ms·

Just to some people know, systemd-resolved does not override /etc/resolv.conf by default. I know because neither Arch not NixOS does this, you need to explicitl

by m45t3r 8y ago

Just to some people know, systemd-resolved does not override /etc/resolv.conf by default. I know because neither Arch not NixOS does this, you need to explicitly override it using `ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf`. The culprit is actually NetworkManager. When it detects that systemd-resolved is running it sets the default resolver to systemd-resolved, and automatically makes the override for the user. I think it also does the same for the other supported resolvers (unbound, dnsmasq, etc.).

m45t3r 8y ago
To fix it, following just the first part of the article is sufficient (setting `dns=none` in NetworkManager configuration). There is no need to remove or disable systemd-resolved, set chattr +i or anything else (of course, if you're not using you can remove it without problems).
- jniedrauer 8y ago
  I thought this was common knowledge. I've been doing this since the upstart days...
fxfan 8y ago
I hear a lot of chatter about nix. What do you use it for and how is it working out for you?
- jordanbeiber 8y ago
  Personally I really like having the whole system configuration declared and checked in to vcs. The way packages are like functions in the nix code repo gives you at least fair confidence that things will actually work as intended. Or at the very least it gives you insight into why it doesn’t. More so compared to a traditional deb/rpm distro in my experience. Not saying it’s perfect by any means, just that it has worked brilliant for a few small projects of mine involving some pi’s. At the workplace though, resistance is high amongst my traditionalist RH/centos co-workers. :)
  - m45t3r 8y ago
    Pretty much what @jordanbeiber described. I recently had to change my work's notebook. Since my NixOS configuration was commited in my dotfiles, I simply restored my NixOS configuration and $HOME and everything was working like the old notebook. Also, bugfix for strange behaviors are written in my NixOS files, so it is like NixOS is my own personal distro.
    - fxfan 8y ago
      One of my pain points with Linux is that every newly installed software thinks its okay to add new fonts that "provide" for traditional ones like Arial. I hope I will find a way to change that in nix but I'm wondering if I go change that in /etc/ and repeat for all machines or I can somehow do it in nix conf
arendtio 8y ago
OT: Recently, I had to learn systemd-resolved likes to take control of port 53 too. For me, this was a problem when I wanted to run a DNS server [1] on that port, to be able to request wildcard certificates from Letsencrypt without using the API of my Domain Provider. [1] https://github.com/joohoi/acme-dns https://github.com/joohoi/acme-dns
- yrro 8y ago
  Doesn't it only bind to 127.0.0.53? That wouldn't get in the way of another nameserver unless you also wanted it to bind to the same address...
  - arendtio 8y ago
    Yes, that is right. Binding the DNS server to the public IP address only was the workaround I choose at the time, but I had to configure it explicitly (default was 0.0.0.0).

by m45t3r 8y ago

m45t3r 8y ago

To fix it, following just the first part of the article is sufficient (setting `dns=none` in NetworkManager configuration). There is no need to remove or disable systemd-resolved, set chattr +i or anything else (of course, if you're not using you can remove it without problems).

jniedrauer 8y ago
I thought this was common knowledge. I've been doing this since the upstart days...

fxfan 8y ago

I hear a lot of chatter about nix. What do you use it for and how is it working out for you?

jordanbeiber 8y ago
Personally I really like having the whole system configuration declared and checked in to vcs. The way packages are like functions in the nix code repo gives you at least fair confidence that things will actually work as intended. Or at the very least it gives you insight into why it doesn’t. More so compared to a traditional deb/rpm distro in my experience. Not saying it’s perfect by any means, just that it has worked brilliant for a few small projects of mine involving some pi’s. At the workplace though, resistance is high amongst my traditionalist RH/centos co-workers. :)
- m45t3r 8y ago
  Pretty much what @jordanbeiber described. I recently had to change my work's notebook. Since my NixOS configuration was commited in my dotfiles, I simply restored my NixOS configuration and $HOME and everything was working like the old notebook. Also, bugfix for strange behaviors are written in my NixOS files, so it is like NixOS is my own personal distro.
  - fxfan 8y ago
    One of my pain points with Linux is that every newly installed software thinks its okay to add new fonts that "provide" for traditional ones like Arial. I hope I will find a way to change that in nix but I'm wondering if I go change that in /etc/ and repeat for all machines or I can somehow do it in nix conf

arendtio 8y ago

OT: Recently, I had to learn systemd-resolved likes to take control of port 53 too. For me, this was a problem when I wanted to run a DNS server [1] on that port, to be able to request wildcard certificates from Letsencrypt without using the API of my Domain Provider. [1] https://github.com/joohoi/acme-dns https://github.com/joohoi/acme-dns

yrro 8y ago
Doesn't it only bind to 127.0.0.53? That wouldn't get in the way of another nameserver unless you also wanted it to bind to the same address...
- arendtio 8y ago
  Yes, that is right. Binding the DNS server to the public IP address only was the workaround I choose at the time, but I had to configure it explicitly (default was 0.0.0.0).