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
I am using NextDNS as host DNS service. This means:
Newere NextDNS will use systemd-resolved with DoT/DoH in systemd-resolved.
Older NextDNS will use its own DNS deamon and replace 127.0.0.1:53 to point itself.
In this case, docker may be confused or ignore these conflict DNS settings. Hence, it will report wrong leak information since the container will point DNS to other places rather than NextDNS,
In that case, with "--net=host", this can prevent the confusion and incompatibility.
The text was updated successfully, but these errors were encountered:
I am using NextDNS as host DNS service. This means:
Newere NextDNS will use systemd-resolved with DoT/DoH in systemd-resolved.
Older NextDNS will use its own DNS deamon and replace 127.0.0.1:53 to point itself.
In this case, docker may be confused or ignore these conflict DNS settings. Hence, it will report wrong leak information since the container will point DNS to other places rather than NextDNS,
In that case, with "--net=host", this can prevent the confusion and incompatibility.
The text was updated successfully, but these errors were encountered: