Announcement date: August 13, 2024
Resolved issues
Status Health API does not load
In DNS Resolver Service v3.11.0, calling the GET
v1/status/health API would not work. This issue has now been
resolved.
DNS Resolver Service Status UI does not load
In DNS Resolver Service v3.11.0, the DNS resolver service diagnostics UI that displays the overall health status of the service would not load. This issue has now been resolved.
DNS Resolver Service caches truncated responses
In DNS Resolver Service v3.11.0, the DNS resolver service would cache a truncated response of a client query with no EDNS UDP size from a BIND forwarder, resulting in truncated cached responses to clients that creates a query loop. This issue has now been resolved.
DNS Resolver Service fails to create namespaces
In DNS Resolver Service v3.11.0, the DNS resolver service would fail to create a namespace due to an inconsistency in the filesystem, resulting in no active namespace on the DNS resolver service. This would cause the DNS resolver service to not match queries to a namespace in the DNS logs and return NXDOMAIN responses to clients. This issue has now been resolved.
Resolved issues
The Discovery Instance does not recognize DNS servers configured as "Other DNS Server" in Address Manager
Previously, the Discovery Instance retrieved information from Address Manager and encountered a DNS server configured with the type "Other DNS Server", the Discovery Instance would not retrieve any information, as the service IP address fields are empty. This issue has now been resolved.