Releases: cloudfoundry/bosh-dns-release
Releases · cloudfoundry/bosh-dns-release
v1.33.0
v1.32.0
- Update golang to 1.18.1 and vendored dependencies
Full Changelog: v1.31.0...v1.32.0
v1.31.0
- Update golang to 1.17
Full Changelog: v1.30.0...v1.31.0
v1.30.0
Updates
- Bumped dependencies (Golang 1.16 vendored libraries)
v1.29.0
Updates
- In order to ease the transition from older versions of
bosh-dns-releasefor folks who may not yet have added SANs to their TLS certificates, theGODEBUGenvironment variable is set tox509ignoreCN=0in thebosh-dnsstart script. For some more information about the underlying issue, read this: https://golang.org/doc/go1.15#commonname. - DNS queries are now properly considered case-insensitive. This should resolve #22 .
- Adds a
recursor_max_retriesconfiguration option to increase the number of times a query will be presented to a configured recursor. (PR #75 , Issue #74 ) - Bumps vendored dependencies.
Fixes
- Documents the
metrics.addressjob property. The most widely useful setting for this property (0.0.0.0), is now explicitly mentioned in the Bosh DNS job spec file.
v1.28.0
Updates
- Updates version of Go used to build the
bosh-dnsrelease to 1.15 - Bumped vendored dependencies
Breaking changes
- the Go.15 change does mean that SANs need to be on Bosh dns certs. A missing SAN will cause an error and attempts to determine link healthiness will not return successfully. The default
smartstrategy for link resolution will return all results if none are perceived healthy which limits the impact somewhat.
v1.27.0
v1.26.0
v1.25.0
Features
- Logging format now defaults to human readable timestamps 549e09e
- Metrics updates for return codes and adds support for internal and external request counting 47aae5e 1771eb2
Updates
Bump dependencies
Known Issues
- If the nameserver and domain supports DNSSEC and the dns cache is on, the first call will fail. Subsequent calls to the cache will succeed. Underlying core-dns issue