elastic / elastic/logstash

DNS lookups failing when `ndots` is specified in /etc/resolv.conf

Open
#7,030 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
1d 4h
Merged PRs (30d)
88

Description

Parent bug: https://bugs.ruby-lang.org/issues/10412

This was fixed and backported into ruby 2.0.0, but as we are targeting 1.9.3, we'll need to patch this ourselves.

Found by @tylerjl.

Reproducing:

```
>> Resolv::DNS.new(nameserver: "8.8.8.8", search: "foo", ndots: 2).getaddress("google.com")
Resolv::ResolvError: DNS result has no information for google.com
```

Looking up a rooted (with `.` at the end) name works, though, indicating this is an ndots/search problem:

```
>> Resolv::DNS.new(nameserver: "8.8.8.8", search: "foo", ndots: 2).getaddress("google.com.")
=> #
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.