mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #1732] Dynamic update no implemented #753
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#753
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 @xaneets on GitHub (Jul 6, 2022).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1732
What is the question?
I can not deal with the dynamic update of dns. I send an update request to the server, it responds with NoImpl. I use sqlite with dnssec.
conf file for NS
I am trying to update the zone in this way
Also I tried using
SyncClient::new(conn)insteadSyncClient::with_signer(conn, signer)After that I get this response:
@bluejekyll commented on GitHub (Jul 11, 2022):
What features are you using to build trust-dns? I think there are a few that are necessary for dynamic updates to work properly, specifically
sqliteand one of thednssecoptions.@xaneets commented on GitHub (Jul 11, 2022):
I solved part of the problem by specifying the default dnssec feature, but now the server returns
Query Refusedwhen trying to dynamically update@bluejekyll commented on GitHub (Jul 11, 2022):
Try this specific dnssec feature:
dnssec-ring@xaneets commented on GitHub (Jul 11, 2022):
After adding this feature, debug log has not changed.Server still responds with a
Query Refused@bluejekyll commented on GitHub (Jul 11, 2022):
There may be a bug here, but I'm not sure at the moment where that would be. This should work, and based on the your logs it looks like the client is signing the message properly. I would check the startup logs and make sure that the keys are being read properly during that phase.
I'll mark this as a bug, and we should build a full end-to-end test to verify the configuration. Today the tests around dynamic update are run as unit tests, not full integration tests, so there may be something amiss between those two.
@xaneets commented on GitHub (Aug 9, 2022):
Have there been any updates?