Skip to content
This repository has been archived by the owner on Dec 5, 2021. It is now read-only.

How to make rancher stop forcing its internal server? #1

Open
kamushadenes opened this issue May 3, 2018 · 2 comments
Open

How to make rancher stop forcing its internal server? #1

kamushadenes opened this issue May 3, 2018 · 2 comments

Comments

@kamushadenes
Copy link

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.

@de-johannes
Copy link

I have the same question! Please help! @fabiomontefuscolo

@fabiomontefuscolo
Copy link
Owner

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants