logstash-filter-dns 3.1.0 → 3.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +3 -0
- data/docs/index.asciidoc +4 -4
- data/logstash-filter-dns.gemspec +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 9787a415f32ce4e75a4e5216f6a5a9a2d0df96da8f2799741070cd0bafe611e9
|
4
|
+
data.tar.gz: 6063f389cfa71eb43d60a93729f283535adf361e3426d57c632a30b1e19d3cd1
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 2217a76de4051faa7ffb537cac220aead754aeca20be664672db9dcbd4e76b3fe579fa9a068990e2016dfadc2991822be7c2ea325e1280b1a3084bbdecef3e70
|
7
|
+
data.tar.gz: 7e56de9e265915709a257308ea08cc9a6ab64a7ba869895a6d3d5817cd3f612514a593d96385b05a5e7850f88417e7ca68b7b5bd8e31b7d5155167b2788ec258
|
data/CHANGELOG.md
CHANGED
@@ -1,3 +1,6 @@
|
|
1
|
+
## 3.1.1
|
2
|
+
- Fixed asciidoc formatting for unordered list and a code sample in docs[#57](https://github.com/logstash-plugins/logstash-filter-dns/pull/57)
|
3
|
+
|
1
4
|
## 3.1.0
|
2
5
|
- Added search domains to the `nameserver` option [#56](https://github.com/logstash-plugins/logstash-filter-dns/pull/56)
|
3
6
|
|
data/docs/index.asciidoc
CHANGED
@@ -127,15 +127,15 @@ number of times to retry a failed resolve/reverse
|
|
127
127
|
===== `nameserver`
|
128
128
|
|
129
129
|
* Value type is <<hash,hash>>, and is composed of:
|
130
|
-
|
131
|
-
|
132
|
-
|
130
|
+
** a required `address` key, whose value is either a <<string,string>> or an <<array,array>>, representing one or more nameserver ip addresses
|
131
|
+
** an optional `search` key, whose value is either a <<string,string>> or an <<array,array>>, representing between one and six search domains (e.g., with search domain `com`, a query for `example` will match DNS entries for `example.com`)
|
132
|
+
** an optional `ndots` key, used in conjunction with `search`, whose value is a <<number,number>>, representing the minimum number of dots in a domain name being resolved that will _prevent_ the search domains from being used (default `1`; this option is rarely needed)
|
133
133
|
* For backward-compatibility, values of <<string,string>> and <<array,array>> are also accepted, representing one or more nameserver ip addresses _without_ search domains.
|
134
134
|
* There is no default value for this setting.
|
135
135
|
|
136
136
|
Use custom nameserver(s). For example:
|
137
137
|
|
138
|
-
[source]
|
138
|
+
[source,ruby]
|
139
139
|
filter {
|
140
140
|
dns {
|
141
141
|
nameserver => {
|
data/logstash-filter-dns.gemspec
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
Gem::Specification.new do |s|
|
2
2
|
|
3
3
|
s.name = 'logstash-filter-dns'
|
4
|
-
s.version = '3.1.
|
4
|
+
s.version = '3.1.1'
|
5
5
|
s.licenses = ['Apache License (2.0)']
|
6
6
|
s.summary = "Performs a standard or reverse DNS lookup"
|
7
7
|
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
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: logstash-filter-dns
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 3.1.
|
4
|
+
version: 3.1.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Elastic
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2019-10-
|
11
|
+
date: 2019-10-24 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|