<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debian on Thaddeus Koenig</title><link>https://www.thaddeuskoenig.com/tags/debian/</link><description>Recent content in Debian on Thaddeus Koenig</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Thaddeus Koenig</copyright><lastBuildDate>Thu, 16 Jan 2025 06:06:24 -0500</lastBuildDate><atom:link href="https://www.thaddeuskoenig.com/tags/debian/index.xml" rel="self" type="application/rss+xml"/><item><title>Wireguard DNS issues with Debian</title><link>https://www.thaddeuskoenig.com/blog/00_legacy_wireguard_dns_debian/</link><pubDate>Thu, 23 Nov 2023 00:00:00 -0500</pubDate><guid>https://www.thaddeuskoenig.com/blog/00_legacy_wireguard_dns_debian/</guid><description>&lt;p&gt;When utilizing debian based distros, I&amp;rsquo;ve run into this issue a lot when I&amp;rsquo;m trying to use wireguard and specify DNS settings:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;/usr/bin/wg-quick: line 31: resolvconf: command not found
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;A lot of this is because of systemd has its own resolvconf so you can simply make a symlink to get wireguard running normally:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;sudo ln -s /usr/bin/resolvectl /usr/local/bin/resolvconf 
&lt;/code&gt;&lt;/pre&gt;</description></item></channel></rss>