boulder/bdns
Jacob Hoffman-Andrews 54b5294651
bdns: fix handling of NXDOMAIN (#6916)
A recent refactoring (https://github.com/letsencrypt/boulder/pull/6906)
started treating NXDOMAIN for a CAA lookup as a hard error, when it
should be treated (from Boulder's point of view) as meaning there is an
empty list of resource records.
2023-05-24 12:16:01 -07:00
..
dns.go bdns: fix handling of NXDOMAIN (#6916) 2023-05-24 12:16:01 -07:00
dns_test.go bdns: fix handling of NXDOMAIN (#6916) 2023-05-24 12:16:01 -07:00
mocks.go Expose Extended DNS Errors (#6906) 2023-05-18 20:43:00 -07:00
problem.go Expose Extended DNS Errors (#6906) 2023-05-18 20:43:00 -07:00
problem_test.go Expose Extended DNS Errors (#6906) 2023-05-18 20:43:00 -07:00
servers.go VA: Support discovery of DNS resolvers via Consul (#6869) 2023-05-12 12:54:31 -04:00
servers_test.go VA: Support discovery of DNS resolvers via Consul (#6869) 2023-05-12 12:54:31 -04:00