Skip to content

Updated Unifi router instructions #1259

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.

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

legoraft
Copy link

@legoraft legoraft commented Jul 4, 2025

What does this PR aim to accomplish?:

The Unifi DNS instructions weren't fully up to date anymore in the docs. I updated the IPv4 tutorial and added some notes on VLANs. The IPv6 instructions couldn't be updated, as I currently don't have an IPv6 address in my home router.

How does this PR accomplish the above?:

I added new images and instructions to the Ubiquiti USG section of the docs.


By submitting this pull request, I confirm the following:

  1. I have read and understood the contributors guide, as well as this entire template. I understand which branch to base my commits and Pull Requests against.
  2. I have commented my proposed changes within the code and I have tested my changes.
  3. I am willing to help maintain this change if there are issues with it later.
  4. It is compatible with the EUPL 1.2 license
  5. I have squashed any insignificant commits. (git rebase)
  6. I have checked that another pull request for this purpose does not exist.
  7. I have considered, and confirmed that this submission will be valuable to others.
  8. I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
  9. I give this submission freely, and claim no ownership to its content.

  • I have read the above and my PR is ready for review. Check this box to confirm

@legoraft legoraft requested a review from a team as a code owner July 4, 2025 15:17
Copy link

netlify bot commented Jul 4, 2025

Deploy Preview for pihole-docs ready!

Name Link
🔨 Latest commit 3aafdbc
🔍 Latest deploy log https://app.netlify.com/projects/pihole-docs/deploys/6867f0a4c078020008e2b1fc
😎 Deploy Preview https://deploy-preview-1259--pihole-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Member

@yubiuser yubiuser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The IPv6 instructions couldn't be updated, as I currently don't have an IPv6 address in my home router.

Even if you don't use IPv6 - are you able to update the screenshots and the instructions? No need to change your local configuration, but it would be nice if we can get rid of the warning about the outdated IPv6 guide...


Scroll down to **IPv6**, and under the **DHCPv6/RDNSS DNS Control** section, uncheck **Auto** if it's enabled and enter Raspi's IPv6 address here. Click **Apply Changes** to have the settings persistently saved.

![Screenshot of USG LAN DHCPv6 settings](../images/routers/usg-lan-dhcpv6.png)

All client devices on your network should now automatically be configured with a single IPv4 and single IPv6 address for DNS resolution. If you don't see your client devices update quickly enough, you *can* toggle Wi-Fi off/on or disconnect the Ethernet cable for a couple of seconds and then reconnect it.

!!! note
The default pi-hole behavior (local requests), doesn't work if you have multiple VLANs. You should switch to another [interface](../ftldns/interfaces.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The default pi-hole behavior (local requests), doesn't work if you have multiple VLANs. You should switch to another [interface](../ftldns/interfaces.md).
The default Pi-hole interface binding behavior ('Allow only local requests'), doesn't work if you have multiple VLANs. You should switch to another [interface](../ftldns/interfaces.md).

I think it does not work with local request only as all request for VLANs go to the router first. Instead of writing

switch to another [interface]

It might be better to suggest directly "Respond only on interace XXX"

@legoraft
Copy link
Author

I'll have a look the coming week, currently not able to check it. It should be possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants