[GH-ISSUE #131] Issue building TRust-DNS 0.10 in Windows #63

New issue

Closed

opened 2026-03-07 22:18:28 +03:00 by kerem · 4 comments

kerem commented

2026-03-07 22:18:28 +03:00

Owner

Originally created by @chaoticsmol on GitHub (May 10, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/131

I've been working today on preparing a build of the software I'm working on for Windows. I've installed OpenSSL according to the description in the Rust-OpenSSL README. By the time cargo gets to trying to compile our TRust-DNS 0.10 dependency, however, it encounters a few errors that appear to relate to TRust-DNS' handling of some OpenSSL data.

Below is a screenshot I took of the errors I'm getting. I'm happy to help out by experimenting with any changes to TRust-DNS in my Windows environment.

Just as a note, one of my colleagues has also experienced the exact same issue separately from me.

Originally created by @chaoticsmol on GitHub (May 10, 2017). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/131 I've been working today on preparing a build of the software I'm working on for Windows. I've installed OpenSSL according to the description in [the Rust-OpenSSL README](https://github.com/sfackler/rust-openssl#windows-msvc). By the time cargo gets to trying to compile our TRust-DNS 0.10 dependency, however, it encounters a few errors that appear to relate to TRust-DNS' handling of some OpenSSL data. Below is a screenshot I took of the errors I'm getting. I'm happy to help out by experimenting with any changes to TRust-DNS in my Windows environment. ![](https://u.nya.is/tbjtzl.png) Just as a note, one of my colleagues has also experienced the exact same issue separately from me.

kerem

2026-03-07 22:18:28 +03:00

closed this issue
added the
bug

tools

platform:windows
labels

kerem commented

2026-03-07 22:18:29 +03:00

Author

Owner

@bluejekyll commented on GitHub (May 10, 2017):

Are you planning to use TLS with TRust-DNS?

I don't have a windows machine to test against, but the AppVeyor tests for both 32 and 64 but appear to be passing. I didn't set those up myself, but it might be worth looking at the AppVeyor build environment.

If you're not using TLS, the fastest path forward will be to disable the default TLS feature. You can do that when compiling trust-dns by passing the '--no-default-features'. If you're relying on the DNSSec validation, then you'll need to turn OpenSSL back on with '--features=openssl'

You can specify all of this in Cargo.toml like this:

'''
trust-dns = { version = "^0.10", default-features = false, features = ["openssl"] }
'''

@bluejekyll commented on GitHub (May 10, 2017): Are you planning to use TLS with TRust-DNS? I don't have a windows machine to test against, but the AppVeyor tests for both 32 and 64 but appear to be passing. I didn't set those up myself, but it might be worth looking at the AppVeyor build environment. If you're not using TLS, the fastest path forward will be to disable the default TLS feature. You can do that when compiling trust-dns by passing the '--no-default-features'. If you're relying on the DNSSec validation, then you'll need to turn OpenSSL back on with '--features=openssl' You can specify all of this in Cargo.toml like this: ''' trust-dns = { version = "^0.10", default-features = false, features = ["openssl"] } '''

kerem commented

2026-03-07 22:18:29 +03:00

Author

Owner

@bluejekyll commented on GitHub (May 10, 2017):

Also of note. I migrated away from tokio-tls by default, and instead swapped in tokio-openssl in 0.10.1. If you really want tokio-tls which implemented over native-tls, then you'll want to also depend on trust-dns-native-tls after upgrading to 0.10.1.

@bluejekyll commented on GitHub (May 10, 2017): Also of note. I migrated away from tokio-tls by default, and instead swapped in tokio-openssl in 0.10.1. If you really want tokio-tls which implemented over native-tls, then you'll want to also depend on trust-dns-native-tls after upgrading to 0.10.1.

kerem commented

2026-03-07 22:18:29 +03:00

Author

Owner

@chaoticsmol commented on GitHub (May 10, 2017):

Thanks so much for the quick response!

It looks like upgrading to 0.10.1 actually resolved the issue I had, so I'll go ahead and close this.

Thanks again!

@chaoticsmol commented on GitHub (May 10, 2017): Thanks so much for the quick response! It looks like upgrading to 0.10.1 actually resolved the issue I had, so I'll go ahead and close this. Thanks again!

kerem commented

2026-03-07 22:18:29 +03:00

Author

Owner

@bluejekyll commented on GitHub (May 10, 2017):

Oh, also, I should mention that AppVeyor only started running after 0.10.0 was cut. So the only version that I know works with Windows is 0.10.1.

@bluejekyll commented on GitHub (May 10, 2017): Oh, also, I should mention that AppVeyor only started running after 0.10.0 was cut. So the only version that I know works with Windows is 0.10.1.

kerem referenced this issue

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

[PR #63] [MERGED] 0.8.0 release #1211