David Cook

Documentation: Recommend against multiple rate_limit handlers with identical distributed storage configuration

1

We ran into an issue when using this handler in a more complex configuration, and I think it might be worth mentioning in the distributed rate limiting documentation, or adding...

**Is your feature request related to a problem? Please describe.** I'm interested in using randomized capitalization as described in [draft-vixie-dnsext-dns0x20-00](https://datatracker.ietf.org/doc/html/draft-vixie-dnsext-dns0x20-00) as a defense-in-depth measure against DNS response spoofing. **Describe the...

This adds a `do_not_query` configuration option to the recursor, and in server configuration files. When resolving names, the recursor will filter out any nameserver addresses that fall into the configured...

Multiple round-trip encoding issues identified by fuzzer

3

I tried running the `message` fuzzer locally, and it produced some failing inputs pretty quickly. The issues I've identified thus far are: - When parsing the CAA issuer-domain-name, if `\.\.`...

Remove incorrect comment about core_hint_black_box

1

This removes a comment from `Cargo.toml` on the `core_hint_black_box` feature. Since #123 partially undid #107, the `core_hint_black_box` feature is still used. FWIW, #107 also removed some documentation about the feature,...

This updates the changelog to include the most recent version. Closes #128.

Replicate extended-dns-errors.com in e2e-tests

2

Starting yesterday, the integration test `client_tests::test_nsec3_query_name_is_soa_name` started failing with "could not validate negative response missing SOA". This test queries for PTR records for `valid.extended-dns-errors.com`. I was just trying to investigate...

Recursor: follow NS referrals other than the first one

1

There are three places in `RecursorDnsHandle` where we call `take(1)` on an iterator of NS records, and then look up A/AAAA records. If there are multiple addresses for the first...

Handling of full stops in labels

4

This issue is following up on previous discussions in #2419 and #2433. Currently, IDNA labels that include a full stop do not get encoded as UTF-8 correctly, because full stops...