Uptime Kuma Addon weird DNS config

Configuration
1

Hi all!
I’m not fully sure if it’s correct place to put question. But i hope it is :wink:
I had issue with my Uptime Kuma addon. It appears that docker configuration for DNS in this addon is a little bit weird:

search local.hass.io
nameserver 127.0.0.11
options ndots:0

DNS at 127.0.0.11? It doesnt use my local network DNS, and since then it cannot resolve DNS queries about my local devices.
Does anybody know how to solve it?
I know i might try to chane /etc/resolv inside container, but AFAIK it wont be persistent.

2

Are you sure it is 11 in the end?
127.0.0.1 is localhost, which means the program will contact the the same machine it is running on.
This can be as intended if a service is running there to forward the requests.
The setup is often seen with programs that scan request for malware sites.

3

Yes, i’m pretty sure, that’s i was also surprised.
Moreover, i can ping that IP:

root@a0d7b954-uptime-kuma:/opt$ ping 127.0.0.11
PING 127.0.0.11 (127.0.0.11) 56(84) bytes of data.
64 bytes from 127.0.0.11: icmp_seq=1 ttl=64 time=0.162 ms

I don’t really uderstood docker how it works in HA, however my setup it’s just default Uptime Kuma installation

4

Seems to be a non-HA docker setup issue then.

5

It could be, but it still official image :smiley:
Maybe some tips how to fix it and build my custom one with docker compose?