starred/hickory-dns

Fork 0

mirror of https://github.com/hickory-dns/hickory-dns.git synced 2026-04-25 03:05:51 +03:00

[GH-ISSUE #110] Feature: Resolver, add trust-dns-resolver #353

New issue

Closed

opened 2026-03-15 22:06:48 +03:00 by kerem · 5 comments

kerem commented

2026-03-15 22:06:48 +03:00

Owner

Originally created by @bluejekyll on GitHub (Mar 27, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/110

Originally assigned to: @bluejekyll on GitHub.

This would be a full resolver that could be used instead of a system resolver.

Originally created by @bluejekyll on GitHub (Mar 27, 2017). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/110 Originally assigned to: @bluejekyll on GitHub. This would be a full resolver that could be used instead of a system resolver.

kerem

2026-03-15 22:06:48 +03:00

closed this issue
added the
enhance
label

kerem commented

2026-03-15 22:07:04 +03:00

Author

Owner

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

see #136

@bluejekyll commented on GitHub (May 23, 2017): see #136

kerem commented

2026-03-15 22:07:09 +03:00

Author

Owner

@msehnout commented on GitHub (Jun 1, 2017):

It would be nice to have something like dnssec-trigger that could be used with trust-dns-resolver. I'm using dnssec-trigger for validation on my laptop and it kind of works, but it'd be nice to have project with more welcoming upstream and not written in plain C.

@msehnout commented on GitHub (Jun 1, 2017): It would be nice to have something like [dnssec-trigger](https://www.nlnetlabs.nl/projects/dnssec-trigger/) that could be used with trust-dns-resolver. I'm using dnssec-trigger for validation on my laptop and it kind of works, but it'd be nice to have project with more welcoming upstream and not written in plain C.

kerem commented

2026-03-15 22:07:14 +03:00

Author

Owner

@bluejekyll commented on GitHub (Jun 1, 2017):

What do you use dnssec-trigger for? It looks like it validates DNSSec RRSIGs if I understood the about page. TRust-DNS does already support this. For the resolver it will just be a matter of swapping in the validating when creating a resolver. I'll try and make sure I have examples for this.

@bluejekyll commented on GitHub (Jun 1, 2017): What do you use dnssec-trigger for? It looks like it validates DNSSec RRSIGs if I understood the about page. TRust-DNS does already support this. For the resolver it will just be a matter of swapping in the validating when creating a resolver. I'll try and make sure I have examples for this.

kerem commented

2026-03-15 22:07:19 +03:00

Author

Owner

@msehnout commented on GitHub (Jun 1, 2017):

dnssec-trigger itself is used just to configure unbound resolver according to my network configuration. It works something like this:
When I connect to a network, NetworkManager has a hook that will send network configuration to dnssec-trigger.
Dnssec-trigger then performs a probing, which means it tries to use DHCP provided resolvers for DNSSec validation.
Then it configures Unbound resolver according to probe results. It should configure unbound in such a way, that internal queries are not sent outside of a corporate network and ideally it should also send reverse queries to the proper resolver.

I hope this explanation is not completely messed up. For more information you can check out this Fedora wiki page:
https://fedoraproject.org/wiki/Networking/NameResolution/DNSSEC

@msehnout commented on GitHub (Jun 1, 2017): dnssec-trigger itself is used just to configure unbound resolver according to my network configuration. It works something like this: When I connect to a network, NetworkManager has a hook that will send network configuration to dnssec-trigger. Dnssec-trigger then performs a probing, which means it tries to use DHCP provided resolvers for DNSSec validation. Then it configures Unbound resolver according to probe results. It should configure unbound in such a way, that internal queries are not sent outside of a corporate network and ideally it should also send reverse queries to the proper resolver. I hope this explanation is not completely messed up. For more information you can check out this Fedora wiki page: https://fedoraproject.org/wiki/Networking/NameResolution/DNSSEC

kerem commented

2026-03-15 22:07:25 +03:00

Author

Owner

@bluejekyll commented on GitHub (Jun 26, 2017):

FYI, I just landed this feature in master. I'll be publishing a crate in the next few days.

For the feature you mentioned above. I'm not sure it's something that I will necessarily work on, but if you want to create an issue for it, we can track it and see if anyone else is interested in that?

@bluejekyll commented on GitHub (Jun 26, 2017): FYI, I just landed this feature in master. I'll be publishing a crate in the next few days. For the feature you mentioned above. I'm not sure it's something that I will necessarily work on, but if you want to create an issue for it, we can track it and see if anyone else is interested in that?

kerem referenced this issue

2026-03-15 22:38:02 +03:00

[GH-ISSUE #353] Switch from net2 to socket2 library #459

kerem referenced this issue

2026-03-16 02:02:58 +03:00

[PR #337] [MERGED] support mDNS #1373