-
-
Notifications
You must be signed in to change notification settings - Fork 562
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
Clarify how and when UQDN are forwarded with conditional forwarding #1873
Conversation
Signed-off-by: DL6ER <[email protected]>
Co-authored-by: XhmikosR <[email protected]>
I probably would reframe this sentence. Reason: default on a fresh installation is having all boxes
Additionally, I would add some hint for the advanced uses (and maybe for us to remember :-) That the option only applies to |
I disagree. On fresh installs, the option will not be set at all in Same for the other box (Never forward reverse lookups for private IP ranges): |
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/pi-hole-ftl-v5-9-web-v5-6-and-core-v5-4-released/49544/1 |
You are right, but something is wrong here. The boxes are ticked in the web interface and also the template of But I tried it two times now on a fresh install and without further modifications both options are removed from the I'm not sure why the lines are removed, because the install script does only replace the |
I think the reason is here: Which deletes As long we don't call ADD An easy solution would be to add Sourcing I can file a PR tomorrow... |
Thanks for your analysis. This definitely needs fixing. |
By submitting this pull request, I confirm the following:
git rebase
)What does this PR aim to accomplish?:
Clarify how and when UQDN are forwarded with conditional forwarding
How does this PR accomplish the above?:
Add more description in the corresponding sections. This is the result of https://discourse.pi-hole.net/t/also-forward-unqualified-host-names-creates-dnssec-loop/49208
What documentation changes (if any) are needed to support this PR?:
This is a documentation change.