vdboor
November 30, 2020, 2:17pm
1
As of iOS 14 / MacOS 11 Big Sur pihole logs a lot of "OTHER" queries.
It turns out this type 65479 record is actually a new SVCB/HTTPS record type. See: Speeding up HTTPS and HTTP/3 negotiation with... DNS
I know this has been discussed before. In light of this new insight, I wonder whether this does make sense to add.
DL6ER
November 30, 2020, 2:19pm
2
Thanks for your suggestion, we're actively monitoring the situation but the SVCB/HTTP type hasn't been standardized yet. The most recent draft of the standard can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/
As you can see over there, the draft is constantly being edited (last edit Nov 2, 2020) so things may still change.
system
December 21, 2020, 2:19pm
3
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
DL6ER
December 31, 2020, 9:56am
5
I transformed this help topic into a feature request yesterday. This feature will be implemented by
pi-hole:development ← pi-hole:new/SVCB_HTTPS
opened 09:42AM - 31 Dec 20 UTC
**By submitting this pull request, I confirm the following:**
- [X] I have re… ad and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md).
- [X] I have checked that [another pull request](https://github.com/pi-hole/FTL/pulls) for this purpose does not exist.
- [X] I have considered, and confirmed that this submission will be valuable to others.
- [X] I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
- [X] I give this submission freely, and claim no ownership to its content.
**How familiar are you with the codebase?:**
## 10
---
Add special handling for `SVCB` and `HTTPS` query types as specified by [this](https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/) IETF draft, section 2. Usually, we would not add query types still in draft mode, however, this time a big player in the market (imagine a bitten into fruit) decided to push something not even yet standardized into the market. Hence, many users are seeing this new query type now. The move from this vendor makes it unlikely that the standard can be much different from the draft (without needing a lot of effort), however, we stay fully flexible with Pi-hole as we're only storing a numeric value in the database and can change its translation into a name at any time.
pi-hole:devel ← pi-hole:new/SVCB_HTTPS
opened 09:55AM - 31 Dec 20 UTC
**By submitting this pull request, I confirm the following:**
- [X] I have r… ead and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md), as well as this entire template.
- [X] I have made only one major change in my proposed changes.
- [X] I have commented my proposed changes within the code.
- [X] I have tested my proposed changes, and have included unit tests where possible.
- [X] I am willing to help maintain this change if there are issues with it later.
- [X] I give this submission freely and claim no ownership.
- [X] It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
- [X] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
---
**What does this PR aim to accomplish?:**
Add `SVCB` and `HTTPS` types and reduce code duplication slightly
**How does this PR accomplish the above?:**
This is the frontend PR corresponding to https://github.com/pi-hole/FTL/pull/1010
This PR works without the FTL changes, however, it also doesn't do anything without them.
(this also means it can be merged independently of the FTL PR).
**What documentation changes (if any) are needed to support this PR?:**
None
1 Like