logstash-filter-dns 3.0.13 → 3.0.14

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2cfb886c7e1e5d133977ad0fb0ed7baa2b8bbf18b7fcfed34eaa6b628e877348
-  data.tar.gz: 762233f5dbb9daee249855da71f7cbb08a2de25d24ecbd48cfaacc4169eb5442
+  metadata.gz: 341ced782cd6b185f99d4f4bee0fd087730be5778d5047db4bdffe8b120078c5
+  data.tar.gz: 497917e8f50a780a61b8ce9d868ed160639373bc0ff2effee9d3d201a9d1cd67
 SHA512:
-  metadata.gz: d557860ea2169bdfc464c1f28fceb1a2bf2d5697b1a997a8844f4e197b167d040d2e8fd177bd4bc4443a68a2cc99d5991a7e93738b2dec04e150f230211d1b10
-  data.tar.gz: 21d68b5a0f08d315db8b30da3e13689a13c57e2e4b10003ff5f94f03b656fface5a5ad04216eaa8d778a9aa86b2134fe2b478c04be349485b7f216758d3ee492
+  metadata.gz: 7551c9b77b2502b20054a84e9ea708d3fd2ff2b861058748e2f7b5f4b4036157cdf939cf37a92c967afd08a6b00ca437ebc28b44ea8a7bda914d2c164bb1176e
+  data.tar.gz: d94d30376359478c31b85a98a6b27facdcb21f295094a5e5dc10e3d59b075ba8c4800e50cebd4098c14964aae4746dfe41df17d6de2d15649b4a2ccaefe229a2

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 3.0.14
+  - Added documentation on the `nameserver` option for relying on `/etc/resolv.conf` to configure the resolver
+
 ## 3.0.13
   - Fixed JRuby resolver bug for versions after to 9.2.0.0 [#51](https://github.com/logstash-plugins/logstash-filter-dns/pull/51)
 

data/docs/index.asciidoc

@@ -129,7 +129,14 @@ number of times to retry a failed resolve/reverse
   * Value type is <<array,array>>
   * There is no default value for this setting.
 
-Use custom nameserver(s). For example: `["8.8.8.8", "8.8.4.4"]`
+Use custom nameserver(s). For example: `["8.8.8.8", "8.8.4.4"]`.
+If `nameserver` is not specified then `/etc/resolv.conf` will be read to
+configure the resolver using the `nameserver`, `domain`,
+`search` and `ndots` directives in `/etc/resolv.conf`.
+
+Note that nameservers normally resolve fully qualified domain names (FQDN)
+and relying on `/etc/resolv.conf` can be useful to provide a domains search
+list to resolve underqualified host names for example.
 
 [id="plugins-{type}s-{plugin}-resolve"]
 ===== `resolve` 

data/lib/logstash/filters/dns.rb

@@ -46,7 +46,14 @@ class LogStash::Filters::DNS < LogStash::Filters::Base
   # specified under `reverse` and `resolve`.
   config :action, :validate => [ "append", "replace" ], :default => "append"
 
-  # Use custom nameserver(s). For example: `["8.8.8.8", "8.8.4.4"]`
+  # Use custom nameserver(s). For example: `["8.8.8.8", "8.8.4.4"]`.
+  # If `nameserver` is not specified then `/etc/resolv.conf` will be read to
+  # configure the resolver using the `nameserver`, `domain`,
+  # `search` and `ndots` directives in `/etc/resolv.conf`.
+  #
+  # Note that nameservers normally resolve fully qualified domain names (FQDN)
+  # and relying on `/etc/resolv.conf` can be useful to provide a domains search
+  # list to resolve underqualified host names for example.
   config :nameserver, :validate => :array
 
   # `resolv` calls will be wrapped in a timeout instance

data/logstash-filter-dns.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
 
   s.name            = 'logstash-filter-dns'
-  s.version         = '3.0.13'
+  s.version         = '3.0.14'
   s.licenses        = ['Apache License (2.0)']
   s.summary         = "Performs a standard or reverse DNS lookup"
   s.description     = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-filter-dns
 version: !ruby/object:Gem::Version
-  version: 3.0.13
+  version: 3.0.14
 platform: ruby
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2019-04-29 00:00:00.000000000 Z
+date: 2019-10-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement