feat(question): name SVCB/LOC/NAPTR record types in logs #120

2026-04-19T12:49:48+08:00

razvandimescu commented

2026-04-19 12:49:48 +08:00

(Migrated from github.com)

Summary

Adds SVCB (64), LOC (29), and NAPTR (35) to the QueryType enum so logs print the type name instead of UNKNOWN(N).
Replaces the private SVCB_QTYPE: u16 = 64 const introduced in #119 with QueryType::SVCB.to_num(), matching the existing HTTPS path.

Why

Issue #114 reports lines like UNKNOWN(64) _dns.resolver.arpa flooding the log. That's RFC 9462 DDR-aware clients probing for encrypted-DNS upgrade — real traffic, not noise. LOC and NAPTR show up in the same user's logs.

Test plan

cargo test --lib — 315 passed
cargo fmt
CI green

## Summary - Adds `SVCB` (64), `LOC` (29), and `NAPTR` (35) to the `QueryType` enum so logs print the type name instead of `UNKNOWN(N)`. - Replaces the private `SVCB_QTYPE: u16 = 64` const introduced in #119 with `QueryType::SVCB.to_num()`, matching the existing HTTPS path. ## Why Issue #114 reports lines like `UNKNOWN(64) _dns.resolver.arpa` flooding the log. That's RFC 9462 DDR-aware clients probing for encrypted-DNS upgrade — real traffic, not noise. LOC and NAPTR show up in the same user's logs. ## Test plan - [x] `cargo test --lib` — 315 passed - [x] `cargo fmt` - [ ] CI green

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dearsky/numa#120