[GH-ISSUE #3045] recurse binary should provide default roots and/or improve docs #1120

New issue

Closed

opened 2026-03-16 01:39:59 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 01:39:59 +03:00

Owner

Originally created by @bdaehlie on GitHub (Jun 12, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3045

I tried to run the "recurse" binary like this:

$ ./recurse --info google.com

It panics, saying it needs "roots", something not mentioned in --help.

It seems to work if I provide a root server IP via the -n flag, but this isn't obvious the way the --help is worded.

It would be nice if the recurse binary provided default roots, and either way, the help text could use some additional clarity.

Originally created by @bdaehlie on GitHub (Jun 12, 2025). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3045 I tried to run the "recurse" binary like this: $ ./recurse --info google.com It panics, saying it needs "roots", something not mentioned in --help. It seems to work if I provide a root server IP via the -n flag, but this isn't obvious the way the --help is worded. It would be nice if the recurse binary provided default roots, and either way, the help text could use some additional clarity.

kerem closed this issue

2026-03-16 01:40:05 +03:00

kerem commented

2026-03-16 01:40:11 +03:00

Author

Owner

@djc commented on GitHub (Jun 12, 2025):

Full error message:

thread 'main' panicked at /Users/djc/src/hickory-dns/crates/recursor/src/recursor_dns_handle.rs:78:9:
roots must not be empty
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@djc commented on GitHub (Jun 12, 2025): Full error message: ``` thread 'main' panicked at /Users/djc/src/hickory-dns/crates/recursor/src/recursor_dns_handle.rs:78:9: roots must not be empty note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ```

kerem commented

2026-03-16 01:40:16 +03:00

Author

Owner

@djc commented on GitHub (Jun 12, 2025):

See #3046.

@djc commented on GitHub (Jun 12, 2025): See #3046.

kerem referenced this issue

2026-03-16 04:20:12 +03:00

[PR #1120] [CLOSED] Bump data-encoding from 2.2.0 to 2.2.1 #1982