[GH-ISSUE #640] Version mismatch: trust-dns-resolver 0.10.1 won't build with tls support #259

New issue

Closed

opened 2026-03-07 23:05:39 +03:00 by kerem · 3 comments

kerem commented

2026-03-07 23:05:39 +03:00

Owner

Originally created by @toreriklinnerud on GitHub (Dec 20, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/640

Describe the bug
trust-dns-resolver 0.10.1 pulls in trust-dns-proto ^0.6.0 and trust-dns-rustls ^0.4.0 pulls in conflicting trust-dns-proto ^0.5.0

To Reproduce

[package]
name = "playground"
version = "0.1.0"
authors = ["tel"]

[dependencies]
trust-dns-resolver = { version = "0.10.1", features = ["dns-over-rustls"] }

extern crate trust_dns_resolver;

fn main() {
}

Expected behavior
Compilation success

System:

OS: macOS
Architecture: x86_64
Version 10.14.2
rustc version: rustc 1.30.0

Version:
Crate: trust-dns-resolver
Version: 0.10.1

Additional context
Previous version builds ("version = "= 0.10.0")

Originally created by @toreriklinnerud on GitHub (Dec 20, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/640 **Describe the bug** `trust-dns-resolver 0.10.1` pulls in `trust-dns-proto ^0.6.0` and `trust-dns-rustls ^0.4.0` pulls in conflicting `trust-dns-proto ^0.5.0` **To Reproduce** ```toml [package] name = "playground" version = "0.1.0" authors = ["tel"] [dependencies] trust-dns-resolver = { version = "0.10.1", features = ["dns-over-rustls"] } ``` ```rust extern crate trust_dns_resolver; fn main() { } ``` **Expected behavior** Compilation success **System:** - OS: macOS - Architecture: x86_64 - Version 10.14.2 - rustc version: rustc 1.30.0 **Version:** Crate: trust-dns-resolver Version: 0.10.1 **Additional context** Previous version builds ("version = "= 0.10.0")

kerem closed this issue

2026-03-07 23:05:44 +03:00

kerem commented

2026-03-07 23:05:50 +03:00

Author

Owner

@bluejekyll commented on GitHub (Dec 21, 2018):

Thank you for the report. I think this just requires a push of the TLS crates. I’ll see about doing that tonight.

@bluejekyll commented on GitHub (Dec 21, 2018): Thank you for the report. I think this just requires a push of the TLS crates. I’ll see about doing that tonight.

kerem commented

2026-03-07 23:05:55 +03:00

Author

Owner

@bluejekyll commented on GitHub (Dec 21, 2018):

resolver 0.10.2 has been published, and should fix this issue.

@bluejekyll commented on GitHub (Dec 21, 2018): resolver 0.10.2 has been published, and should fix this issue.

kerem commented

2026-03-07 23:06:00 +03:00

Author

Owner

@toreriklinnerud commented on GitHub (Dec 21, 2018):