Describe the bug

Commit b1cb5d468ef881d5efdf86efadf423e0b59c0ee2 added a hardcoded "resolver 127.0.0.11 ipv6=off" line to the nginx.conf configuration file that prevents zigbee2mqtt-windfront from properly running when deployed on Kubernetes vs Docker given that inside Kubernetes the default local dns server is not 127.0.0.11.

The solution starts up correctly, however, given that nginx cannot contact the local dns resolver, it continuously fails when attempting to connect to the zigbee2mqtt instances configured.

Inside the container image entrypoint scripts there is a script that gathers the locally configured dns server from /etc/resolv.conf and applies it to some portions of the configuration of the container. Couldn't the same logic be used to dynamically adjust the resolver line of the nginx.conf file or an environment variable be added in order to support these specific use cases?

To Reproduce

Deploy the container image inside Kubernetes

Expected behavior

No response

Affected browsers

Chrome

Stacktrace