mirror of
https://github.com/charlesabarnes/SPFtoolbox.git
synced 2026-04-25 03:16:18 +03:00
[GH-ISSUE #40] Feature Request #18
Labels
No labels
Good First Issue
bug
enhancement
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SPFtoolbox#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jpgpi250 on GitHub (Feb 5, 2020).
Original GitHub issue: https://github.com/charlesabarnes/SPFtoolbox/issues/40
I'm using pihole (an adblocker), listening on port 53, addresses 127.0.0.1 and 192.168.2.57.
pihole forwards all requests, not on the blacklist, to unbound port 5552, addresses 127.10.10.2 or fdaa:bbcc:ddee:2::5552 (local addresses, same host).
The result is, when trying to resolve a domain on the blacklist, using pihole, the response will be 0.0.0.0 or ::
When submitting the request to unbound, the response will be the real address of the domain.
Pihole, unbound and SPFtoolbox (hosted on lighttpd) are all running on the same machine.
It would be a great improvement if there was a configuration file, specifying the possible resolvers, something like:
127.0.0.1#53
192.168.2.57#53
127.10.10.2#5552
fdaa:bbcc:ddee:2::5552#5552
and a dropdown selection box in the web interface (php scripts) to select a resolver, used by SPFtoolbox to provide the requested DNS information.
Don't know if this is possible, would be a great improvement if it was (I would create a topic on the pihole forum to recommend this tool as a trouble shooting option).