<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dns on Linux Security</title><link>https://linuxtransfer.com/tags/dns/</link><description>Recent content in Dns on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 22 May 2026 10:04:50 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming systemd-resolved: Tips for Troubleshooting and Customizing DNS Resolution on Linux</title><link>https://linuxtransfer.com/post/2026-05-22-taming-systemd-resolved-tips-for-troubleshoot/</link><pubDate>Fri, 22 May 2026 10:04:50 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-05-22-taming-systemd-resolved-tips-for-troubleshoot/</guid><description>&lt;h2 id="introduction-to-systemd-resolved">Introduction to systemd-resolved&lt;/h2>
&lt;p>I&amp;rsquo;ve been using systemd-resolved for a while now, and I have to say, it&amp;rsquo;s a big improvement over traditional DNS resolvers. As of 2026, many Linux distributions, including Ubuntu, Debian, and Fedora, have adopted systemd-resolved as the default DNS resolver. While it offers several benefits, including improved security and performance, some users may encounter issues or require customization to suit their specific needs. Don&amp;rsquo;t bother with trying to disable it, though - it&amp;rsquo;s usually worth the effort to get it working right.&lt;/p></description></item></channel></rss>