Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that the router does not always have to be the DHCP server #967

Merged
merged 1 commit into from
Jun 16, 2019
Merged

Clarify that the router does not always have to be the DHCP server #967

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions settings.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -868,11 +868,11 @@ function convertseconds($argument)
determine the names of devices on your local network. As a
result, tables such as Top Clients will only show IP addresses.</p>
<p>One solution for this is to configure Pi-hole to forward these
requests to your home router, but only for devices on your
requests to your DHCP server (most likely your router), but only for devices on your
home network. To configure this we will need to know the IP
address of your router and the name of your local network.</p>
address of your DHCP server and the name of your local network.</p>
<p>Note: The local domain name must match the domain name specified
in your router, likely found within the DHCP settings.</p>
in your DHCP server, likely found within the DHCP settings.</p>
<div class="form-group">
<div class="checkbox">
<label><input type="checkbox" name="conditionalForwarding" value="conditionalForwarding"
Expand Down