Pihole & Unbound: Installation for Pihole V6 #2508
MickLesk
started this conversation in
Breaking Changes
Replies: 1 comment
-
I had to disable the built-in NTP Server too: [ntp.ipv4]
# Should FTL act as network time protocol (NTP) server (IPv4)?
active = false ### CHANGED, default = true
[ntp.ipv6]
# Should FTL act as network time protocol (NTP) server (IPv6)?
active = false ### CHANGED, default = true |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Pi-hole v6 Migration Guide
Overview
With the release of Pi-hole v6, significant changes have been introduced, particularly in the way configurations are managed. This guide outlines the key changes and provides a migration path for users, especially those utilizing Unbound as their upstream DNS resolver.
Key Changes in Pi-hole v6
Migration to TOML Configuration
/etc/pihole/pihole.toml
instead ofsetupVars.conf
for settings.Updated Unbound Configuration Handling
setupVars.conf
ordnsmasq.d/01-pihole.conf
for upstream DNS must be adjusted.pihole.toml
.DHCP Server Defaults Changed
NTP Sync Changes
pihole.toml
.New Command-Line Configuration Options
pihole-FTL --config
.Migration Steps
1. Verify Migration
Pi-hole v6 automatically migrates existing configurations and stores previous versions in:
After updating, check the migration log to ensure a smooth transition.
2. Adjust Upstream DNS (for Unbound Users)
If you previously modified
setupVars.conf
, update/etc/pihole/pihole.toml
as follows:Modify the
[dns]
section:Restart Pi-hole:
3. Ensure DHCP Settings (if used)
For those using Pi-hole as a DHCP server, ensure it is enabled in
pihole.toml
:Apply the changes:
4. Disable NTP Sync (if needed)
By default, NTP sync is active. To disable it, modify:
Apply the change:
pihole-FTL --config ntp.sync.active false
Common Issues & Fixes
Issue:
no upstream servers configured
Fix: Ensure
upstreams
is properly set inpihole.toml
and restart Pi-hole:Issue: DHCP Not Working After Update
Fix: Verify that
[dhcp] active = true
is set and restart Pi-hole.Summary
Pi-hole v6 introduces automatic configuration migration but requires manual updates for Unbound users. Ensure your DNS settings are correctly configured in
pihole.toml
, verify DHCP settings, and adjust NTP synchronization if necessary.For further details, refer to the official Pi-hole documentation.
Beta Was this translation helpful? Give feedback.
All reactions