Skip to content
Discussion options

You must be logged in to vote

So, after much debugging on my end, I found that I had to manually mount an up-to-date version of root.zone. This removes the error, but using podman exec -ti unbound-server drill -DT badsig.go.dnscheck.tools, I get:

Output
$ podman exec -ti unbound-server drill -DT badsig.go.dnscheck.tools
Warning: No trusted keys were given. Will not be able to verify authenticity!
;; Domain: .
;; Signature ok but no chain to a trusted key or ds record
[S] . 172800 IN DNSKEY 257 3 8 ;{id = 20326 (ksk), size = 2048b}
. 172800 IN DNSKEY 256 3 8 ;{id = 26470 (zsk), size = 2048b}
. 172800 IN DNSKEY 256 3 8 ;{id = 53148 (zsk), size = 2048b}
. 172800 IN DNSKEY 257 3 8 ;{id = 38696 (ksk), size = 2048b}
Checki…

Replies: 5 comments 11 replies

Comment options

You must be logged in to vote
1 reply
@TheRettom
Comment options

Comment options

You must be logged in to vote
1 reply
@TheRettom
Comment options

Comment options

You must be logged in to vote
3 replies
@TheRettom
Comment options

@madnuttah
Comment options

@TheRettom
Comment options

Comment options

You must be logged in to vote
2 replies
@TheRettom
Comment options

Answer selected by TheRettom
@madnuttah
Comment options

Comment options

You must be logged in to vote
4 replies
@madnuttah
Comment options

@TheRettom
Comment options

@madnuttah
Comment options

@TheRettom
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #92 on March 17, 2025 08:49.