1.3.0

API Changes from 1.2.1:

• Added the TransportOptions.httpQueryParamName property with a default value of dns.
• Added the Message.authority and Message.additional properties, populated if a message contains answers in those sections.
• Added the NSEC and NSEC3 record type and associated data types.
• Added the SystemResolver class

Changes

• [NEW]: DNSKit can now send requests to the configured DNS resolver of the system
• [NEW]: DNSKit now supports decoding punycode-encoded IDNA domain names
• [NEW]: DNSKit now supports authenticated NXDOMAIN responses with NSEC and NSEC3 records

1.2.1

API Changes from 1.2.0:

• Added the TransportOptions.useHttp2 property with a default value of true.

Changes

• [PARTIAL FIX] The DNS over HTTPS client regains support for HTTP/2 servers as is recommended by the RFC. However, this is only a partial fix as HTTP/2 support is mutually exclusive with bootstrap IP support. If one or more bootstrap IPs are defined for a DoH query, HTTP/1.1 is used, despite a request to use HTTP2 with the useHttp2 property. (See #11 for more details including background and justification).
• [FIXED] The WHOIS client would return a failure if it could not follow a redirect and get a result from that, even if it already had gotten at least one successful result.

1.2.0

API Changes from 1.1.1:

• The Query type now takes in an array of server addresses rather than just a single address. The client will attempt to connect to all of these addresses, returning the first successful result (successful meaning any DNS reply).
• The Query.execute methods return a new Response type, which contains the reply message as well as the server that produced this reply.
• The Query.validateConfiguration method now accepts an array of server IP addresses, as well as an optional array of bootstrap IP addresses for DoH servers.

Changes

• [ADDED] New TransportOptions.httpsBootstrapIps property which can contain an array of IP addresses that DNSKit will directly connect to for DNS over HTTPS requests. This can save an additional bootstrap DNS request when looking up the DoH server. Both IPv4 and IPv6 addresses can be specified.
• [FIXED] DNS TXT records over >255B are now parsed correctly (#8).
• [FIXED] Invalid IP addresses were reported as having an incorrect port in the error message.

1.1.1

API Changes from 1.0.10:

• Added property userAgent: String? to TransportOptions

Changes

• [ADDED] Override default User-Agent header value for DNS over HTTPS requests
• [FIXED] DNS over HTTPS requests now provide an Accept: header
• [FIXED] DNS over HTTPS requests use a DNS message ID of 0, conforming to the RFC

1.1.0

API Changes from 1.0.10:

• Added QUIC = "quic" case to enum TransportType
• Added LOC = 29 case to enum RecordType
• Added new type LOCRecordData

Changes

• [ADDED] DNS over Quic Support (RFC 9250)
• [ADDED] DNS LOC record support (RFC 1876)

1.0.10

API Changes from 1.0.9:

None

Changes

• [FIXED]: Crash when performing DNSSEC validation on a TLD (#4)

1.0.9

API Changes from 1.0.8:

None

Change

• [NEW]: IP addresses will automatically be converted into appropriate PTR labels when performing a PTR query. For example, querying PTR 8.8.4.4 will now automatically convert the name to 4.4.8.8.in-addr.arpa. IPv4 and IPv6 are supported.
• [IMPROVED]: WHOIS data updated.
• [IMPROVED]: Various documentation improvements.

1.0.8

API Changes from 1.0.7:

None

Change

• [FIX]: Crash on WHOIS lookup for bare gTLDs
• [FIX]: Crash on parsing corrupt DNS messages

1.0.7

API Changes from 1.0.6:

• The zoneDelegation property of DNSSECResult and associated ZoneDelegation type have been removed. The zoneDelegation was never populated or used.

Change

• [FIX]: Fix DNSSEC validation for cross-zone CNAME records

1.0.6

API Changes from 1.0.5:

None

Change

• [FIX]: Fix zone DNSSEC verification for zones with multiple DS records