BoemeltreinandGitHub
79e9c7ad55
**Description** <!-- helmify docs --> ⚒️ Fixes # <!--(issue)--> **⚙️ Type of change** - [ ] ⚙️ Feature/App addition - [ ] 🪛 Bugfix - [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 🔃 Refactor of current code - [x] 📜 Documentation Changes **🧪 How Has This Been Tested?** <!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration --> **📃 Notes:** <!-- Please enter any other relevant information here --> **✔️ Checklist:** - [ ] ⚖️ My code follows the style guidelines of this project - [ ] 👀 I have performed a self-review of my own code - [ ] #️⃣ I have commented my code, particularly in hard-to-understand areas - [x] 📄 I have made changes to the documentation - [ ] 🧪 I have added tests to this description that prove my fix is effective or that my feature works - [ ] ⬆️ I increased versions for any altered app according to semantic versioning - [x] I made sure the title starts with `feat(chart-name):`, `fix(chart-name):`, `chore(chart-name):`, `docs(chart-name):` or `fix(docs):` **➕ App addition** If this PR is an app addition please make sure you have done the following. - [ ] 🖼️ I have added an icon in the Chart's root directory called `icon.png` --- _Please don't blindly check all the boxes. Read them and only check those that apply. Those checkboxes are there for the reviewer to see what is this all about and the status of this PR with a quick glance._
1.7 KiB
1.7 KiB
title
| title |
|---|
| Automatic Split DNS with PiHole |
Using Blocky in conjunction with PiHole enables seamless automated split DNS functionality.
:::danger[unrecommended configuration]
The below guide is not the recommended DNS solution for TrueCharts. We recommend running Blocky from the premium train in a standalone configuration. Setting up your DNS as outlined below adds complexity and will reduce reliability.
:::
Deploy Blocky
:::note[Blocky]
Blocky includes k8s Gateway which automates the split DNS process. We will be using Blocky in between PiHole and your upstream DNS servers of choice to resolve your domain.
:::
- Deploy Blocky
- Make sure k8s-Gateway is enabled.
- Assuming you would like to use PiHole for Allow/Deny list, configure Blocky that those list from blocky are disabled. To disable the Blocky Deny lists this can be used in the deployment of Blocky:
clientGroupsBlock:
[]
Deploy PiHole
Deploy PiHole with the following configuration:
- Namespace needs to be
privileged - Set a loadBalancerIP or Ingress to the
mainservice - Set a loadBalancerIP to the
dnsservice FTLCONF_webserver_api_password, here you need to pick a password for the PiHole WebGUI.FTLCONF_dns_upstreams, here you need to set your Blocky DNS address.
Example configuration:
env:
FTLCONF_dns_upstreams: "${BLOCKY_IP}"
FTLCONF_webserver_api_password: "DitIsSuperGeheim"
Configure Router
- Configure your router to use your PiHole DNS when configuring DNS clients. You will need to consult your router manual for this as each router is different. In above example, the router should be configured to use 192.168.1.221 as the DNS server.