On Mon, Nov 17, 2014 at 5:09 PM, Chris Adams <li...@cmadams.net> wrote:
> Once upon a time, Juan Orti <juan.o...@miceliux.com> said: > > systemd-resolved is a daemon for resolving DNS. What's wrong about > > caching? All DNS servers perform caching. > > > > It's like if you have unbound at 127.0.0.1 as local resolver, that's a > > very common setup. > > Well, that's the point. We already have multiple, perfectly functional, > caching resolvers. We have resolver libraries. Why did the systemd > project add this to the scope of the project for "a system and service > manager for Linux"? Why didn't they re-use existing services and/or > libraries? Why re-invent a wheel that happens to have a number of > corner cases that can be tricky to get right (and a security problem if > you get it wrong)? > > In general DNS caching may be useful, but with other perfectly good solution(s) (i.e. nscd) for Linux the implementation of the same in systemd does not add value.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
