Nameserver 192.168.65.1 incorrect filebeat container

[SteveDoeve]

Hello,

I receive the following error when starting the filebeat container:

2019-01-22T09:25:25.738Z INFO pipeline/output.go:93 Attempting to reconnect to backoff(elasticsearch(http://elasticsearch:9200)) with 1 reconnect attempt(s)
2019-01-22T09:25:25.765Z WARN transport/tcp.go:53 DNS lookup failure "elasticsearch": lookup elasticsearch on 192.168.65.1:53: no such host
2019-01-22T09:25:27.765Z ERROR pipeline/output.go:100 Failed to connect to backoff(elasticsearch(http://elasticsearch:9200)): Get http://elasticsearch:9200: lookup elasticsearch on 192.168.65.1:53: no such host

For example the logstash container does not have this issue and I found a difference in the resolv.conf.

Wrong .conf:
nameserver 192.168.65.1
domain home

logstash and kibana conf (works)
nameserver 127.0.0.11
options ndots:0

The problem is when I change it for filebeat nothing happens and I am still unable to resolve "elasticsearch".

2019-01-22T09:39:05.221Z INFO pipeline/output.go:93 Attempting to reconnect to backoff(elasticsearch(http://elasticsearch:9200)) with 6 reconnect attempt(s)
2019-01-22T09:39:05.223Z WARN transport/tcp.go:53 DNS lookup failure "elasticsearch": lookup elasticsearch on 127.0.0.11:53: read udp 127.0.0.1:54728->127.0.0.11:53: read: connection refused

Whats also an issue is that whenever I restart the filebeat container the resolv.conf is set back to the wrong values.