Backward Compatibility Warning
This release removes support for DynamoDB as a database. If you happen to be using DynamoDB, you will need to migrate to MySQL. If you need assistance please reach out in the gitter channel
New Features
- Added ability to specify TSIG key algorithm in both the configuration file, via the API on zone connect / update, and via the portal. Support additional key algorithms including
HMAC-MD5, HMAC-SHA1, HMAC-SHA224, HMAC-SHA256, HMAC-384, HMAC-SHA512. If not specified, defaults toHMAC-MD5
Improvements
- Support Default AWS Credentials Provider - previously SQS and Route 53 only supported access + secret key credentials. If you omit the access and secret keys in configuration now, both SQS and Route 53 will fall back to the Default credential chain lookup mechanism. More info can be found here - https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/DefaultAWSCredentialsProviderChain.html
- Increase size of review comment text box in the portal
Bug Fixes
- Route 53 SOA records now properly loaded into VinylDNS
- Unable to connect to Route 53 zone - this was due to a few bugs with FQDN determination and differences between public and private hosted zones. Route 53 public and private zones can now be connected in VinylDNS