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 Dec 5, 2021. It is now read-only.
How do you prevent rancher from commenting out the Resolving Servers you add and using only its rancher-dns server? I know it uses the specified resolving servers when the internal metadata doesn't known about the domain queried, but that kind of defeats the purpose of this project.
How did you managed to avoid that? Getting out of Managed networking doesnt look like a good idea.
The text was updated successfully, but these errors were encountered:
Sorry guys, there are a long I don't play with Rancher. At that time, I think I changed something in Docker daemon, but I don't have access to the server anymore to check the complete solution. Probably, the company I was working for, the @hacklabr, they moved to Kubernetes.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello! Nice project you got there.
How do you prevent rancher from commenting out the Resolving Servers you add and using only its rancher-dns server? I know it uses the specified resolving servers when the internal metadata doesn't known about the domain queried, but that kind of defeats the purpose of this project.
How did you managed to avoid that? Getting out of Managed networking doesnt look like a good idea.
The text was updated successfully, but these errors were encountered: