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

Compute reply time also for queries which failed upstream #1234

Merged
merged 1 commit into from
Oct 27, 2021

Conversation

DL6ER
Copy link
Member

@DL6ER DL6ER commented Oct 27, 2021

By submitting this pull request, I confirm the following:

  • I have read and understood the contributors guide.
  • I have checked that another pull request for this purpose does not exist.
  • I have considered, and confirmed that this submission will be valuable to others.
  • I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
  • I give this submission freely, and claim no ownership to its content.

How familiar are you with the codebase?:

10


Fixes #1233

The issue is that we did not compute the reply time for queried that failed upstream. The API interprets the lack of a computed reply time as "there was no reply" which is wrong here.

@DL6ER DL6ER added the Bugfix label Oct 27, 2021
@DL6ER DL6ER requested a review from yubiuser October 27, 2021 17:58
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.

Confirm working and fixing #1233

Bildschirmfoto zu 2021-10-27 20-05-20

@DL6ER DL6ER merged commit 60b056f into development Oct 27, 2021
@DL6ER DL6ER deleted the fix/DNSSEC_BOGUS_reply_time branch October 27, 2021 18:25
@DL6ER DL6ER mentioned this pull request Dec 20, 2021
5 tasks
@pralor-bot
Copy link

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-12-web-v5-9-and-core-v5-7-released/51795/1

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

Successfully merging this pull request may close these issues.

3 participants