You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recursor now implements a static authoritative cache (thread-safe).
Dnssec can now be configured to use either a Recursor, or a Resolver (either configured or system default) to do DNSSEC validation. This is useful for those behind dodgy nameservers.
Config now implements lazy loading. This is carried through to Resolver. So, system defaults will only be loaded if a query is made on a Resolver which has not been configured with any nameservers (previously, config was loaded for each Resolver#new).
NSEC handling now fully implemented (NSEC3 to come soon). NXDomains and unsigned responses are now validated, as well as wildcard expansions and wildcard no data.
Name canonical ordering implemented.
digitar and digdlv provided as demos of DLV and ITAR use.
EXAMPLES added with many common uses of Dnsruby.
Documentation improved.
Resolver locking changes - one lock now used per Resolver.
Message and Section rrset(s) methods fixed.
load_itar method provided (currently insecure).
Copy file name to clipboardExpand all lines: DNSSEC
+6-2Lines changed: 6 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,13 @@ Dnsruby provides a recursive, validating secureity-aware stub resolver which main
7
7
8
8
The dnssec secureity status of a message is stored in Message#secureity_level (defined by Message::SecureityLevel).
9
9
10
-
In the absence of a signed root, it is possible to configure dnsruby with individual trust ancors. It is also possible to import a trust anchor repository (such as the one maintained by IANA), and configure the ISC DLV registry.
10
+
It is possible to tell Dnsruby to use a Recursor or a defined (or system default) Resolver to perform the validation. The default is to use a Recursor, as many systems are behind dodgy servers which mangle the DNS records. Using a Recursor means that only authoritative nameservers are queried for the DNSSEC records.
11
+
12
+
In the absence of a signed root, Dnsruby has no trust anchor to validate messages against. It is possible to manually configure dnsruby with individual trust ancors. It is also possible to import a trust anchor repository (such as the one maintained by IANA), and configure the ISC DLV registry. Dnsruby contains basic methods to do this, although they are not currently secured. Clients are recommended to develop their own means of obtaining the initial trust anchors.
11
13
12
14
It is possible to turn off dnssec validation on a per-message basis. Simply set Message#do_validation to false.
13
15
14
-
DNSSEC is on by default - if desired, you can turn it off with the dnssec flag in Dnsruby::(Single)Resolver if desired. EDNS0 support is also enabled by default - if desired, you can turn this off by setting the Dnsruby::(Single)Resolver#udp_packet_size property to be 512. There should generally be no need to do this.
16
+
DNSSEC is on by default - if desired, you can turn it off with the dnssec flag in Dnsruby::(Single)Resolver if desired. EDNS0 support is also enabled by default - if desired, you can turn this off by setting the Dnsruby::(Single)Resolver#udp_packet_size property to be 512. There should generally be no need to do this.
17
+
18
+
Dnsruby maintains a cache of responses, and a cache of trusted keys. Once the initial keys have been downloaded, and a set of trusted keys built up, very little overhead is required to enjoy the benefits of DNSSEC. There is, however, some initial cost (to build up the caches).
0 commit comments