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.

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

Set DNSSEC indicator color to non-red for local upstream resolver. #64

Open
dschaper opened this issue Sep 20, 2019 · 6 comments · Fixed by #411
Open

Set DNSSEC indicator color to non-red for local upstream resolver. #64

dschaper opened this issue Sep 20, 2019 · 6 comments · Fixed by #411

Comments

@dschaper
Copy link
Member

Is your feature request related to a problem? Please describe.
Currently DNSSEC is a red Disabled status when DNSSEC is not enabled. In some cases DNSSEC is not desirable and the red color gives the impression of an error state.

Describe the solution you'd like
If /etc/pihole/setupVars.conf shows 127.0.0.1 or similar for upstream then set the color to a neutral shade, it's neither good nor bad. Suggest blue as an indicator of nominal condition.

@mwoolweaver
Copy link
Contributor

mwoolweaver commented Feb 11, 2025

can i extend this request to include DHCP as well

Image

@rdwebdesign rdwebdesign mentioned this issue Feb 12, 2025
1 task
@rdwebdesign rdwebdesign linked a pull request Feb 12, 2025 that will close this issue
1 task
@yubiuser
Copy link
Member

@mwoolweaver

Just a hint: Looking at your screenshot, it looks like you run PADD directly on your Pi-hole device. Did you know, with v6 you can even run it remotely from any other device which can connect to your Pi-hole.
Just run ./padd.sh --server IP_of_your_Pi-hole

@mwoolweaver
Copy link
Contributor

mwoolweaver commented Feb 13, 2025

How does the password work when 2FA is enabled? Same as WebUI?

@yubiuser
Copy link
Member

You need to create/use the 'app password' for all applications (including PADD) that don't implement 2FA.

@mwoolweaver
Copy link
Contributor

this should have closed with #411 or #412, right?

@yubiuser
Copy link
Member

Yes. It will autoclose when this is merged into master branch

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

Successfully merging a pull request may close this issue.

4 participants