13 ms·
Sad news today: systemd-resolved to be deployed in Ubuntu 16.10
- voltagex_ 10y ago>- It accepts DNS forwarders for all its interfaces. That means if you are on wifi and 3g, or ethernet and wifi, you have more than one DNS server from logically different networks. With no way of guaranteeing which logical network you asking. That's going to be very inconvenient for laptop users...
- gonzo 10y agoAnd any phone or tablet that uses it
- steventhedev 10y agoHow does this play out with wifi networks that resolve dns requests for say, "google.com" with their "click to accept the terms of your municipal free wifi" page?
- bazzargh 10y agoI use a mac and the same issue is there; all I do is override the DNS on the wireless connection to use 8.8.8.8. In systemd-land, I'd expect that to be in /etc/systemd/wireless.network: [Match] Name=wlan0 [Network] DNS=8.8.8.8 (other settings omitted). However, DNS hijacking isn't necessary for a captive portal - they can reroute port 80 traffic and respond with 511 per https://tools.ietf.org/html/rfc6585#section-6 https://tools.ietf.org/html/rfc6585#section-6, (quite common now as the interaction is better for non-browser phone apps) or advertise the login page via DHCP as in https://tools.ietf.org/html/rfc7710 https://tools.ietf.org/html/rfc7710.
- steventhedev 10y agonot necessary, and yet very common. And setting your DNS server to 8.8.8.8 doesn't help when they reply with their internal gateway for all DNS requests. FYI - android fires a request to http://clients3.google.com/generate_204 http://clients3.google.com/generate_204, I'm fairly confident windows/ios/mac/ubuntu all do something similar.
- corney91 10y agoI'm not sure how it's supposed to work -- are you only supposed to have DNS servers defined from one particular network, or is it a case of needing to specify priority of sets of DNS servers? Or is there any software that allows you to configure domain names for particular interfaces?
- akerro 10y agoI just gave up on Linux distributions and switched to FreeBSD. Every year there are more steps backward in every Linux disto than good changes.
- naivepiano 10y agoI see that this change (systemd) is mostly driven by desktop software dev teams. If linux chooses to care mostly about the desktop aspect (IMHO previous such experiments like Unity were total flops but I'm not an expert) instead of its server one then maybe that's the opportunity for BSDs to cover up the void. Not a bad thing at all.
- akerro 10y agoNo, I think it's good change. Last year I stopped contributing to ArchLinux, I'm seriously considering doing the same for FreeBSD/PC-BSD now. BSDs have a lot to catch-up, even things like network-manager don't work on BSD, it have to be ported, or network connections have to be configured manually in rc files. Personally it's ok for me to work like that. OpenVPN configuration in FBSD was EASIER than doing the same in UI on KDE5 nm-applet. (Personal opinion->) I think connection to VPN providers is more stable and I lose less data on BSD than on Arch. So it was another benefit :) Generally a lot of things are much easier in BSDs, there is literally ONE manual for everything and it applies from FBSD-NetBSD-OpenBSD-DragonFlyBSD. When one manual for a thing for ArchLinux doesn't apply to Ubuntu or even worse tutorial from Ubuntu doesn't work on Debian, things become ugly... I value it a lot.
- 3princip 10y agoI have used Linux (mainly Ubuntu) exclusively for years and love it. I do some devops when needed, run a few websites etc. Granted, I'm not a full-time sysadmin but I do plenty of work with Linux. I don't understand why systemd is taking over or what benefit it has bought. It works for now, is that enough? It feels like a monstrosity of overly complex and questionable design. Yet, it spreads. Throwing "unix philosophy", a most agreeable set of ideas, out the window. Maybe I'm just being reactionary and slow to adapt.
- Macuyiko 10y agoI agree. First the whole thing about systemd closing nohup and screen processes on logout and now this... I have been thinking about switching to freebsd as well, at least for my server environments. Any good recommendations re: Linux distros that follow the Unix philosophy closely whilst still being up to date in terms of packages?
- akerro 10y agoThe last on battle field are Void Linux, Slackware and Getnoo.
- thde 10y agoDon't forget Alpine Linux
- dkarapetyan 10y agoI started using freebsd two weeks ago. My usual ruby stack carried over just fine and so far it's kinda fun. The stack being sinatra, thin, nginx, postgresql. I assume any other sane backend stack will carry over just as easily.
- snaky 10y agohttps://wiki.gentoo.org/wiki/Gentoo_Without_systemd https://wiki.gentoo.org/wiki/Gentoo_Without_systemd
- fridsun 10y ago
- vidarh 10y agoI'm conflicted about this. I've yet to find a Linux distribution that actually acts the way the documentation for /etc/resolv.conf claims the options in resolv.conf should work (most of the options do nothing or work differently than you'd expect). Basically, if you rely on the system/glibc provided DNS resolution on most Linux distros and you want reliability, your best bet is to run a local DNS server and point everything there either way. That's not changing with systemd-resolved in the state it is today, but who knows, maybe someone actually paying attention to the resolver stub will finally make that situation improve.
- JdeBP 10y ago> most of the options do nothing or work differently than you'd expect Please give examples.
- abgrant 10y agoSad indeed. Every IT product reaches a stage where the basic things are done. Then bloat is added to keep programmers employed and to create new problems that secure a steady income from consulting. But perhaps I'm biased: I just had to use chattr to keep the &/!&%"/! NetworkManager from overwriting /etc/resolv.conf. All these things just worked 10 years ago.
- pmlnr 10y ago> All these things just worked 10 years ago. While I massively dislike the systemd approach, this is not true either. Using wifi, mobile connections on linux were a massive pain unless you already spent countless hour on writing your own fixes for you own setup.
- snaky 10y agoDon't use NetworkManager at all, that's it.
- justinsaccount 10y ago> All these things just worked 10 years ago 10 years ago most resolvers did not use source port randomization no one had DNSSEC deployed.
- JdeBP 10y ago10 years ago would be 2006. In 2006, three of the most popular DNS server softwares, djbdns, PowerDNS (ranked third in a contemporary survey of content DNS servers), and MaraDNS, all had source port randomization. As did mine, although its ranking was somewhat lower. (-: djbdns had had it since the previous century, MaraDNS for 5 years, mine for roughly the same, and PowerDNS for (I think) 1.
- justinsaccount 10y agoI said resolvers, not servers. What client side dns libraries did source port randomization in 2006?
- mianos 10y agoDebian anyone?
- i_have_to_speak 10y agoDebian 8 comes with systemd. There is a fork [1], but not really popular. [1] https://devuan.org/ https://devuan.org/
- misterwavey 10y agoit'd be funny to fork devuan and replace init with systemd.
- snaky 10y agohttps://github.com/tmux/tmux/issues/428#issuecomment-222195317 https://github.com/tmux/tmux/issues/428#issuecomment-2221953...
- tener 10y agoIf systemd is so horrible why is everyone switching to it? EDIT: This is an honest question. I read quite a few negative comments on it and yet people in charge seem to be convinced this is the way forward. I'm curious why.
- naivepiano 10y agoI don't know about other distros but let me remind you that ubuntu sometime ago switched from gnome desktop to Unity despite all the cries that the latter is just horrible.
- dorfsmay 10y agoBut you can still run gnome on Ubuntu (I do), and Linux without a graphical interface at all.
- naivepiano 10y agoTrue. Or you can switch to Mint. The think with systemd though is that you don't have this option anymore. Regardless of how bad idea you think it is - you are stuck with it (as it seems). I think that's on the core of arguments against it.
- snaky 10y agoWithout "Desktop Environment", not without graphical interface.
- 10y ago
- sunseb 10y agoSystemd is arguably the most hated Linux software ever. Why have all major distros switched to this thing ? I don't get it.
- AlgorithmicTime 10y agoThe one thing it does do is push responsibility for init scripts off of package maintainers onto upstream. Which explains it, I believe.
- akerro 10y agoLess time spent maintaining init scripts.
- byuu 10y agoSo, less than zero minutes for the vast majority of desktop users? Hell I barely even touch init (rc.d) scripts on my BSD servers.
- pmlnr 10y agoWhen was the last time you had to "maintain" an init script? Apart from the rare cases when you have to write one, which is mostly start-stop-daemon and a switch-case, when was it really a pain in the past ~8-9 years?
- akerro 10y agoThe last time I had to setup execution order of 7 scripts and make sure 3rd starts after 1st is already running? https://www.reddit.com/r/linux/comments/4m0r93/why_did_archlinux_embrace_systemd/d3rm4xh https://www.reddit.com/r/linux/comments/4m0r93/why_did_archl...
- snaky 10y agodepend() { need net before inetd before xinetd } https://wiki.gentoo.org/wiki/Handbook:X86/Working/Initscripts#Writing_initscripts https://wiki.gentoo.org/wiki/Handbook:X86/Working/Initscript...
- Philipp__ 10y agoWhat really struck me was the fact that desktop community (not sure if this would be happiest word for it, but I think you'll understand) is dictating the fate of whole Linux. For me Linux was and is primary a server OS. Than worsktation one, and on the last spot consumer desktop OS. I mean for desktop perspective systemd maybe isn't that bad, but for servers I am sure there are better solutions.
- maheart 10y agoI maintain Linux servers. I also write backend/server software. systemd is a Godsend. It's infinitely easier to write a systemd init script, than it is to write a robust init script in shell. systemd (by leveraging cgroups) makes it easier to 'track' started processes. It makes it easier to stop/kill processes. It also provides handy security features (e.g. PrivateTmp).
- nisa 10y agoCan we stop talking about the init scripts? systemd does that well, we all got it. I personally was not overwhelmed when having to use it but it's step forward from sysv init scripts - no one sane doubts that. All the recent talk about systemd is about the other components that replace certain basic userland compoments. logind for sessions changed the default to kill background tasks on logout, now it's about the implementation of the dns resolver that comes with systemd. There are other implementations that replace cron, ntpd, syslog...etc.pp. All of this has a dependency on glibc and uses dbus. This has nothing to do with init scripts. This is an attempt to improve on the status quo of userland tools close to the OS. systemd appears to provide some minimal userland that comes with a Linux kernel and aims to be a userland API. I personally think this is a bad idea but I kind of see the point why you might want to do this. The IMHO absolutely warranted criticism for some of these replacements is that they are not better designed, that they create new dependencies and complicate things without reason and there is a tendency to create some systemd specific API that userland has to implement - breaking compatibility with other POSIX systems - something that was hard to do even before systemd. So it's not about init scripts - it's about revamping essential userland tools in a way that's badly designed according to some. Personally I hold no grudge against this but I'm not keen on using this or having to deal with this as a sysadmin. It's a undocumented black box once you have run into problems and you are busy reading C code or capturing dbus calls. I have usually better things to do. And for the initscripts - you could have done this with runit/s6 and mkdir with cgroups in 2008 if you wanted. You could have used setsid before that. This was deprecated and now systemd (or something else that implements the kernel API) is the whole mananger of cgroups. I personally think the systemd way is not the right direction to take as it's horrible inflexible and will bite Linux but I can understand why you might disagree here strongly.
- userbinator 10y agoThe process turns a request for binary DNS data into into XML, feeds it into the sytemd/dus ecosystem, which turns it into binary DNS to send it to the forwarder. The binary DNS answer then gets turned into XML goes through systemd/dbus, then is turned back into binary DNS to feed back into glibc. This reminds me of http://thedailywtf.com/articles/XXL-XML http://thedailywtf.com/articles/XXL-XML and the "XML fever" that infected most of the enterprise and otherwise software developers many years ago. Whenever I see some system XML-ifying everything, it's usually a good indicator of grotesque complexity elsewhere in it too.
- deleted 10y ago[deleted]
- scrollaway 10y agoHow else would you send the data to dbus? dbus is xml-based. This is caused by resolved requiring a separate forwarder. "XML" isn't inherently bad.
- cesarb 10y ago> dbus is xml-based "D-Bus is low-overhead because it uses a binary protocol, and does not have to convert to and from a text format such as XML." https://dbus.freedesktop.org/doc/dbus-specification.html https://dbus.freedesktop.org/doc/dbus-specification.html
- wtbob 10y ago> dbus is xml-based. No, it's not: https://dbus.freedesktop.org/doc/dbus-specification.html https://dbus.freedesktop.org/doc/dbus-specification.html > "XML" isn't inherently bad. Yes, it is (well, as a data format; as a markup language it's ugly but serviceable). XML is incredibly verbose, arcanely complex and a colossal time-sink of man-hours which could have been spent on pretty much anything else in computing. It's the JavaScript of data formats (which is amusing, since JavaScript's data format JSON is actually not half bad).
- deleted 10y ago[deleted]
- dkarapetyan 10y agoMy new dev/deploy target is freebsd. It's actually kinda nice. It treats the user with respect and doesn't pretend to know better.
- yousry 10y agosudo systemctl stop systemd-resolved sudo systemctl disable systemd-resolved After that you can use whatever you like.
- pmontra 10y agoI'm surprised that so many comments are about systemd, if it is evil or not, and so few about this actual issue. Is a system with this DNS implementation safe, would it work, is something you want to use? Maybe the author is biased but the list of issues and potential vulnerabilities is so long that there could be CVEs reserved now waiting only for the release of software.
- insulanian 10y agoWhat are some good resources for getting up to speed with systemd quickly for a web dev who didn't do extensive Linux administration besides setting up hosting on EC2 instances with nginx and REST API controlled by supervisor (software)?
- pas 10y agohttps://www.digitalocean.com/community/tutorials/systemd-essentials-working-with-services-units-and-the-journal https://www.digitalocean.com/community/tutorials/systemd-ess... for the bare minimum http://linoxide.com/linux-how-to/systemd-boot-process/ http://linoxide.com/linux-how-to/systemd-boot-process/ for how it starts up https://lwn.net/Articles/604609/ https://lwn.net/Articles/604609/ cgroups https://lwn.net/Articles/531114/ https://lwn.net/Articles/531114/ namespaces https://dvdhrm.wordpress.com/2013/07/08/thoughts-on-linux-system-compositors/ https://dvdhrm.wordpress.com/2013/07/08/thoughts-on-linux-sy... logind/sessions/seats http://0pointer.net/blog/projects/socket-activated-containers.html http://0pointer.net/blog/projects/socket-activated-container... and finally "the series" from the horse's mouth :)
- vamur 10y agoSystemd sounds good in theory until you cannot disable systemd-journald and it grows to 50M RAM. And out of nowhere dozens of gvfsd* processes are spawned for no apparent reason.
- JdeBP 10y agoIt's interesting to contrast Paul Wouters' dismissal of source port randomization with the conversation on the Ubuntu mailing list with Martin Pitt, the systemd developer and Ubuntu systemd maintainer whose announcement precipitated M. Wouters' critique. > > source port randomization is enabled by default to further protect against DNS spoofing attacks. > [...] source port randomization is pretty useless [...] -- Paul Wouters, https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html https://lists.dns-oarc.net/pipermail/dns-operations/2016-Jun... > ATM resolved uses randomized ID fields [...]. It does not use source port randomization though, -- Martin Pitt, https://lists.ubuntu.com/archives/ubuntu-devel/2016-May/039364.html https://lists.ubuntu.com/archives/ubuntu-devel/2016-May/0393... > I'm concerned what this says about the maturity of the project: djbdns introduced source port randomization back in 1999. -- Seth Arnold, https://lists.ubuntu.com/archives/ubuntu-devel/2016-May/039370.html https://lists.ubuntu.com/archives/ubuntu-devel/2016-May/0393...
- JdeBP 10y ago> It uses nsswitch to basically take over gethostbyname() and getaddrinfo(). This means any software using a DNS library like ldns, unbound, bind, knot, etc bypasses this system and gets an inconsistent DNS view from the rest of the system. It explicitly does not support those kind of applications. > It won't work well with applications that have their own DNS code inside. Such as browsers. The systemd developers have addressed M. Wouters' charges as follows. Such applications are classed as > legacy software which does not use libnss-resolve -- https://github.com/systemd/systemd/issues/3420#issuecomment-223245328 https://github.com/systemd/systemd/issues/3420#issuecomment-... and > legacy DNS clients -- https://github.com/systemd/systemd/issues/3420#issuecomment-223253526 https://github.com/systemd/systemd/issues/3420#issuecomment-... The systemd developers maintain that > programs really should use NSS (with nss-resolve as backend) or resolved's native bus APIs, but not talk DNS themselves. -- https://github.com/systemd/systemd/issues/3420#issuecomment-223253526 https://github.com/systemd/systemd/issues/3420#issuecomment-...