[dns-operations] Sad news today: systemd-resolved to be deployed in Ubuntu 16.10

[Ondřej Surý]

Hmm,

could we perhaps provide an alternative implementation as a replacement for systemd-resolved that would provide the same services on top of getdns?

Cheers,
--
 Ondřej Surý -- Technical Fellow
 --------------------------------------------
 CZ.NIC, z.s.p.o.    --     Laboratoře CZ.NIC
 Milesovska 5, 130 00 Praha 3, Czech Republic
 mailto:ondrej.sury at nic.cz    https://nic.cz/
 --------------------------------------------

----- Original Message -----
> From: "Paul Vixie" <paul at redbarn.org>
> To: "Ondřej Surý" <ondrej.sury at nic.cz>
> Cc: "Ralf Weber" <dns at fl1ger.de>, dns-operations at dns-oarc.net
> Sent: Friday, June 3, 2016 2:12:19 PM
> Subject: Re: [dns-operations] Sad news today: systemd-resolved to be deployed in Ubuntu 16.10

> Ondřej Surý wrote:
>> I already spoke to Martin, and he is very open about that decision
>> (it's still very early in the development cycle), so I think that
>> this still might be reverted if we don't slip into systemd-ranting
>> and provide reasons why this has bad design (not just bugs).
> 
> systemd, launchd, and libc, and mpr, and every other place where dns
> client logic is needed, should just link against getdns, and not try to
> understand or to improve upon the best available dns client logic.
> 
> if getdns isn't desireable for some reason then use ldns or lwdnsd.
> 
> where systemd went wrong was trying to understand and improve.
> 
> --
> P Vixie