- Fixed an issue where a non-string value existing in the resolve/reverse field could cause the plugin to crash #65
- Replaced Timeout::timeout block with
Resolv::DNS::timeouts=
#62 - Added restriction for ruby version > 2.0, effectively making Logstash 6.x+ a requirement #62
- Fixed an issue where each missed lookup could result in unreclaimed memory (jruby bug) by handling lookup misses without raising exceptions #61
- Added restriction on JRuby resolv.rb patch to versions prior to 9.2.9.0 #58
- Fixed asciidoc formatting for unordered list and a code sample in docs#57
- Added search domains to the
nameserver
option #56
- Added documentation on the
nameserver
option for relying on/etc/resolv.conf
to configure the resolver
- Fixed JRuby resolver bug for versions after to 9.2.0.0 #51
- Fixed issue where unqualified domains would fail to resolve when running this plugin with Logstash 5.x #48
- Fixed crash that could occur when encountering certain classes of invalid inputs #49
- Fixed JRuby resolver bug for versions prior to 9.1.16.0 #45
- Log timeouts as warn instead of error #43
- Allow concurrent queries when cache enabled #42
- Logging improvement to include DNS resolution failure reason #36
- Fix bug where forward lookups would not cache timeout errors
- Update gemspec summary
- Fix some documentation issues
- Log a warning on missing resolve/reverse fields rather than crashing
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Add support for International Domain Names e.g. müller.com. Fixes logstash-plugins#22
- Add support for custom hosts files (helps with testing but could be useful to some folks).
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- Fix spec early termination by removing an explicit return from a block
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Add caches for failed and successful lookups
- Lower default timeout value
- Retry a maximum of :max_retries instead of failing immediately
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0