Site update
This commit is contained in:
parent
66311ee207
commit
44f8726e2d
34 changed files with 472 additions and 458 deletions
|
@ -12,19 +12,12 @@
|
|||
Setup dns with adblock and dot/doh with pi-hole and unbound - Crony Akatsuki
|
||||
|
||||
</title>
|
||||
<meta property="og:url" content="https://cronyakatsuki.xyz/blog/setup-dns-pihole-unbound/">
|
||||
<meta property="og:site_name" content="Crony Akatsuki's Website">
|
||||
<meta property="og:title" content="Setup dns with adblock and dot/doh with pi-hole and unbound">
|
||||
<meta property="og:description" content="Just another day I seted up my own private dns server that has adblocking ( and other stuff ) using pihole and uses unbound as a resolver. To safelly connect to the dns server I’m using DNS over HTTPS for my browser’s and HTTPS over TLS for stuffy for my whole desktop and private dns in android ( Android has DoH support but only for google and cloudflare right now). Let’s get on to setting everything up">
|
||||
<meta property="og:locale" content="en_us">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="article:section" content="blog">
|
||||
<meta property="article:published_time" content="2023-09-27T00:00:00+00:00">
|
||||
<meta property="article:modified_time" content="2023-09-27T00:00:00+00:00">
|
||||
<meta property="article:tag" content="Self-Host">
|
||||
<meta property="article:tag" content="Dns">
|
||||
<meta property="article:tag" content="Pi-Hole">
|
||||
<meta property="article:tag" content="Unbound">
|
||||
<meta property="og:title" content="Setup dns with adblock and dot/doh with pi-hole and unbound" />
|
||||
<meta property="og:description" content="Just another day I seted up my own private dns server that has adblocking ( and other stuff ) using pihole and uses unbound as a resolver. To safelly connect to the dns server I’m using DNS over HTTPS for my browser’s and HTTPS over TLS for stuffy for my whole desktop and private dns in android ( Android has DoH support but only for google and cloudflare right now). Let’s get on to setting everything up" />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://cronyakatsuki.xyz/blog/setup-dns-pihole-unbound/" /><meta property="article:section" content="blog" />
|
||||
<meta property="article:published_time" content="2023-09-27T00:00:00+00:00" />
|
||||
<meta property="article:modified_time" content="2023-09-27T00:00:00+00:00" /><meta property="og:site_name" content="Crony Akatsuki's Website" />
|
||||
|
||||
</head>
|
||||
|
||||
|
@ -64,12 +57,23 @@
|
|||
<hr>
|
||||
</div>
|
||||
|
||||
<p>Just another day I seted up my own private dns server that has adblocking ( and other stuff ) using pihole and uses unbound as a resolver. To safelly connect to the dns server I’m using DNS over HTTPS for my browser’s and HTTPS over TLS for stuffy for my whole desktop and private dns in android ( Android has DoH support but only for google and cloudflare right now). Let’s get on to setting everything up</p>
|
||||
<p>Just another day I seted up my own private dns server that has adblocking ( and
|
||||
other stuff ) using pihole and uses unbound as a resolver. To safelly connect to
|
||||
the dns server I’m using DNS over HTTPS for my browser’s and HTTPS over TLS for
|
||||
stuffy for my whole desktop and private dns in android ( Android has DoH support
|
||||
but only for google and cloudflare right now). Let’s get on to setting
|
||||
everything up</p>
|
||||
<!-- raw HTML omitted -->
|
||||
<h2 id="1-pihole">1. Pihole</h2>
|
||||
<p>Let’s start with setting up pihole. I will be installing it with their script on a debian system for easier unbound integration ( unbound doesn’t have an official docker container ).</p>
|
||||
<p>I recommend to read up on the pihole’s docs on exactly how to install it since pihole get’s frequent updates. <a href="https://docs.pi-hole.net/main/basic-install/">DOCS</a></p>
|
||||
<p>I recommend you to install the admin page for easier managmenet and ability to change the upstream dns server ( needed for changing it to unbound later on ). To be able to access the admin page I use an nginx configuration like this one.</p>
|
||||
<p>Let’s start with setting up pihole. I will be installing it with their script on
|
||||
a debian system for easier unbound integration ( unbound doesn’t have an
|
||||
official docker container ).</p>
|
||||
<p>I recommend to read up on the pihole’s docs on exactly how to install it since
|
||||
pihole get’s frequent updates.
|
||||
<a href="https://docs.pi-hole.net/main/basic-install/">DOCS</a></p>
|
||||
<p>I recommend you to install the admin page for easier managmenet and ability to
|
||||
change the upstream dns server ( needed for changing it to unbound later on ).
|
||||
To be able to access the admin page I use an nginx configuration like this one.</p>
|
||||
<div class="highlight"><pre tabindex="0" style="color:#c6d0f5;background-color:#303446;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-nginx" data-lang="nginx"><span style="display:flex;"><span><span style="color:#ca9ee6">server</span> {
|
||||
</span></span><span style="display:flex;"><span> <span style="color:#81c8be">server_name</span> <span style="color:#a6d189">example.com</span> ;
|
||||
</span></span><span style="display:flex;"><span>
|
||||
|
@ -104,14 +108,22 @@
|
|||
</span></span><span style="display:flex;"><span> <span style="color:#81c8be">listen</span> <span style="color:#a6d189">[::]:80</span>;
|
||||
</span></span><span style="display:flex;"><span> <span style="color:#81c8be">return</span> <span style="color:#ef9f76">404</span>; <span style="color:#737994;font-style:italic"># managed by Certbot
|
||||
</span></span></span><span style="display:flex;"><span><span style="color:#737994;font-style:italic"></span>}
|
||||
</span></span></code></pre></div><p>The main point of this config is the <code>/admin</code> location that you need to pass the lighttpd port to acces the website, you can just do it on your main website also.
|
||||
Also to make lighttpd work with nginx listening on port 80 you need to edit the <code>server.port</code> to port you wan’t to use in lighttpd config file located at <code>/etc/lighttpd/lighttpd.conf</code> and then just restart lighttpd</p>
|
||||
</span></span></code></pre></div><p>The main point of this config is the <code>/admin</code> location that you need to pass the
|
||||
lighttpd port to acces the website, you can just do it on your main website
|
||||
also. Also to make lighttpd work with nginx listening on port 80 you need to
|
||||
edit the <code>server.port</code> to port you wan’t to use in lighttpd config file located
|
||||
at <code>/etc/lighttpd/lighttpd.conf</code> and then just restart lighttpd</p>
|
||||
<h2 id="2-unbound">2. Unbound</h2>
|
||||
<p>For this part I will just link the pi-hole’s unbound documentation because it is the most correct one and updated as things change regulary.
|
||||
<p>For this part I will just link the pi-hole’s unbound documentation because it is
|
||||
the most correct one and updated as things change regulary.
|
||||
<a href="https://docs.pi-hole.net/guides/dns/unbound/">Pi-hole unbound docs</a></p>
|
||||
<h2 id="3-dns-over-tls">3. DNS over TLS</h2>
|
||||
<p>For dns over tls you need to first have a ssl certificate. I recommend on using certbot to generate one with this command <code>certbot --nginx -d dot.example.com</code>.</p>
|
||||
<p>Next you will need a reverse proxy, in my case I use nginx. You will need to add this configuration to your main nginx config located at <code>/etc/nginx/nginx.conf</code>. <strong>Make sure to add this outside of the http block and change example.com to your domain</strong></p>
|
||||
<p>For dns over tls you need to first have a ssl certificate. I recommend on using
|
||||
certbot to generate one with this command <code>certbot --nginx -d dot.example.com</code>.</p>
|
||||
<p>Next you will need a reverse proxy, in my case I use nginx. You will need to add
|
||||
this configuration to your main nginx config located at <code>/etc/nginx/nginx.conf</code>.
|
||||
<strong>Make sure to add this outside of the http block and change example.com to your
|
||||
domain</strong></p>
|
||||
<div class="highlight"><pre tabindex="0" style="color:#c6d0f5;background-color:#303446;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-nginx" data-lang="nginx"><span style="display:flex;"><span><span style="color:#ca9ee6">stream</span> {
|
||||
</span></span><span style="display:flex;"><span> <span style="color:#81c8be">log_format</span> <span style="color:#a6d189">basic</span> <span style="color:#a6d189">'</span><span style="color:#f2d5cf">$remote_addr</span> <span style="color:#a6d189">[</span><span style="color:#f2d5cf">$time_local]</span> <span style="color:#f2d5cf">$protocol</span> <span style="color:#f2d5cf">$status</span> <span style="color:#f2d5cf">$bytes_sent</span> <span style="color:#f2d5cf">$bytes_received</span> <span style="color:#f2d5cf">$session_time</span> <span style="color:#f2d5cf">$upstream_addr'</span>;
|
||||
</span></span><span style="display:flex;"><span>
|
||||
|
@ -141,9 +153,14 @@ Also to make lighttpd work with nginx listening on port 80 you need to edit the
|
|||
</span></span><span style="display:flex;"><span> <span style="color:#81c8be">proxy_timeout</span> <span style="color:#a6d189">1s</span>;
|
||||
</span></span><span style="display:flex;"><span> }
|
||||
</span></span><span style="display:flex;"><span>}
|
||||
</span></span></code></pre></div><p>Also make sure to enable port 853, example ufw command is <code>ufw allow 853/tcp</code>. Then restart nginx, to test if this configuration is working you can use your android phone by setting the private dns address to <code>dot.example.com</code> and then visit the website<a href="https://dnsleaktest.com">dnsleaktest</a></p>
|
||||
</span></span></code></pre></div><p>Also make sure to enable port 853, example ufw command is <code>ufw allow 853/tcp</code>.
|
||||
Then restart nginx, to test if this configuration is working you can use your
|
||||
android phone by setting the private dns address to <code>dot.example.com</code> and then
|
||||
visit the website<a href="https://dnsleaktest.com">dnsleaktest</a></p>
|
||||
<h2 id="4-dns-over-https">4. DNS over HTTPS</h2>
|
||||
<p>For using dns over https we will be installing additional package called dnsdinst. On debian systems just run <code>apt install dnsdinst</code>. Next you will need to setup dnsdinst config and restart it. Make sure to change example.com.</p>
|
||||
<p>For using dns over https we will be installing additional package called
|
||||
dnsdinst. On debian systems just run <code>apt install dnsdinst</code>. Next you will need
|
||||
to setup dnsdinst config and restart it. Make sure to change example.com.</p>
|
||||
<pre tabindex="0"><code class="language-conf" data-lang="conf">-- dnsdist configuration file, an example can be found in /usr/share/doc/dnsdist/examples/
|
||||
|
||||
-- disable security status polling via DNS
|
||||
|
@ -160,7 +177,11 @@ newServer({address="127.0.0.1", name="Pi-hole", checkName="e
|
|||
|
||||
-- Create local DOH server listener in DNS over HTTP mode, otherwise the information coming from nginx won't be processed well
|
||||
addDOHLocal("127.0.0.1:5300", nil, nil, "/dns-query", { reusePort=true })
|
||||
</code></pre><p>Next we will need another ssl certificate for the doh domain, for that we will once again using certbot with this command <code>certbot --nginx -d doh.example.com</code>after that add this configuratin to nginx either in sites-available and linking it to sites enabled or in http block in main nginx configuration.</p>
|
||||
</code></pre><p>Next we will need another ssl certificate for the doh domain, for that we will
|
||||
once again using certbot with this command
|
||||
<code>certbot --nginx -d doh.example.com</code>after that add this configuratin to nginx
|
||||
either in sites-available and linking it to sites enabled or in http block in
|
||||
main nginx configuration.</p>
|
||||
<div class="highlight"><pre tabindex="0" style="color:#c6d0f5;background-color:#303446;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-nginx" data-lang="nginx"><span style="display:flex;"><span><span style="color:#737994;font-style:italic"># Proxy Cache storage - so we can cache the DoH response from the upstream
|
||||
</span></span></span><span style="display:flex;"><span><span style="color:#737994;font-style:italic"></span><span style="color:#ca9ee6">proxy_cache_path</span> <span style="color:#a6d189">/var/run/doh_cache</span> <span style="color:#a6d189">levels=1:2</span> <span style="color:#a6d189">keys_zone=doh_cache:10m</span>;
|
||||
</span></span><span style="display:flex;"><span>
|
||||
|
@ -210,13 +231,17 @@ addDOHLocal("127.0.0.1:5300", nil, nil, "/dns-query", { reusePor
|
|||
</span></span></span><span style="display:flex;"><span><span style="color:#737994;font-style:italic"></span> <span style="color:#81c8be">proxy_set_header</span> <span style="color:#a6d189">X-Forwarded-For</span> <span style="color:#f2d5cf">$proxy_add_x_forwarded_for</span>;
|
||||
</span></span><span style="display:flex;"><span> }
|
||||
</span></span><span style="display:flex;"><span>}
|
||||
</span></span></code></pre></div><p>After restarting nginx with this configuration you can it to your web browser as a DNS over HTTPS resolver and once again checkout <a href="https://dnsleaktest.com">dnsleaktest</a> website and check if it is all working.</p>
|
||||
<p>Hope this has been helpfull and if anybody has any way on how to make this guied better you can open a pull request or make an issue on the website’s <a href="https://code.cronyakatsuki.xyz/crony/website">repo</a>.</p>
|
||||
</span></span></code></pre></div><p>After restarting nginx with this configuration you can it to your web browser as
|
||||
a DNS over HTTPS resolver and once again checkout
|
||||
<a href="https://dnsleaktest.com">dnsleaktest</a> website and check if it is all working.</p>
|
||||
<p>Hope this has been helpfull and if anybody has any way on how to make this guied
|
||||
better you can open a pull request or make an issue on the website’s
|
||||
<a href="https://git.cronyakatsuki.xyz/crony/cronyakatsuki.xyz">repo</a>.</p>
|
||||
</div>
|
||||
</main>
|
||||
<footer>
|
||||
<div id="links">
|
||||
<span><a href="https://code.cronyakatsuki.xyz">Code</a></span>
|
||||
<span><a href="https://git.cronyakatsuki.xyz">Code</a></span>
|
||||
<span>|</span>
|
||||
<span><a href="https://steamcommunity.com/id/CronyAkatsuki/">Steam</a></span>
|
||||
<span>|</span>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue