You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
Is it feasible for dnsname to listen at 127.0.0.11? This address is used by docker and some containers assume this to work, hardcoding the address. On podman otoh, places the dns server in the container network range.
Of course hardcoding 127.0.0.11 isn't great form, but it's out there in the wild and supporting it will improve dnsname usability.
For instance, it will help with nginx's resolver config item, which must be set for nginx to resolve names dynamically instead of at startup only.
The text was updated successfully, but these errors were encountered:
This is something we have to consider for the network rewrite. If we write a new dns server we should definitely do this to not block port 53 on the host.
Is it feasible for dnsname to listen at 127.0.0.11? This address is used by docker and some containers assume this to work, hardcoding the address. On podman otoh, places the dns server in the container network range.
Of course hardcoding 127.0.0.11 isn't great form, but it's out there in the wild and supporting it will improve dnsname usability.
For instance, it will help with nginx's
resolver
config item, which must be set for nginx to resolve names dynamically instead of at startup only.The text was updated successfully, but these errors were encountered: