mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #2000] dns of util got a not same behaviour with named on querying from quic server #842
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#842
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 @hingbong on GitHub (Aug 16, 2023).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2000
What is the question?
When I am using
dnscommand, I gotand I set up named with config
./target/release/trust-dns -c forwarder.toml -z ./tests/test-data/test_configs/ -p 24141I got
How to modify the config to make it work?
Thanks
@bluejekyll commented on GitHub (Aug 22, 2023):
Can you share the configuration you used when compiling? I'm not sure why you're having an issue. There is also the
resolvecommand, which is closer to the subsystem used by the Forwarder in trust-dns. Do you think you could see if that command produces different behavior?resolveis closer tonslookupwhereasdnsis closer todig.@hingbong commented on GitHub (Aug 22, 2023):
I built it just using
cargo build --release -p trust-dns -F dns-over-https-rustls -F dns-over-quic -F resolver -F recursorto build, will it use different cert, such as ones from system and the others from somewhere?@hingbong commented on GitHub (Aug 22, 2023):
And I am on Windows.
@bluejekyll commented on GitHub (Sep 6, 2023):
I wonder if this is related to here: #2015
@hingbong commented on GitHub (Oct 9, 2023):
I've updated to commit
45bd92f4ac07ef7d9fa1830a6b596239d01302da, and get this with same config, it looks like related to #2038@djc commented on GitHub (Oct 10, 2023):
cc @daxpedda
@hingbong commented on GitHub (Oct 10, 2023):
I compiled it for OpenWRT and it got a same result, so it's not a Windows-only issue.
@daxpedda commented on GitHub (Oct 11, 2023):
I'm not entirely familiar with the CLI, but as far as I can see:
root certificates seem to be missing.
Doesn't include a crate feature that pulls in certificates. On the other hand, I just realized, we messed up in #2005 because the
trust-dnsCLI doesn't seem to include any root certificates or crate features to enable them. I will make a PR soonish.