-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Add logging for CNAME inspection #832
Conversation
…in that caused blocking the entire CNAME chain. Signed-off-by: DL6ER <dl6er@dl6er.de>
Signed-off-by: DL6ER <dl6er@dl6er.de>
Signed-off-by: DL6ER <dl6er@dl6er.de>
…ase during import. This ensures restarting FTL does not mean we lost this information. Signed-off-by: DL6ER <dl6er@dl6er.de>
d29f0d2
to
e661bd5
Compare
Signed-off-by: DL6ER <dl6er@dl6er.de>
… CNAME chain are already in the cache Signed-off-by: DL6ER <dl6er@dl6er.de>
…This also simplifies the terminology in the CNAME inspection routine. Signed-off-by: DL6ER <dl6er@dl6er.de>
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/regex-engine-improvements/34751/61 |
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-2-released/36964/1 |
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/top-blocked-domain-not-showing-who-was-blocked/39217/21 |
By submitting this pull request, I confirm the following:
How familiar are you with the codebase?:
10
additional_info column
to queries table. We fill it with the domain that caused blocking the entire CNAME chain.additional_info
field