Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kube-dns should be first and only DNS server for Windows pods #147

Closed
PatrickLang opened this issue May 24, 2018 · 1 comment
Closed

kube-dns should be first and only DNS server for Windows pods #147

PatrickLang opened this issue May 24, 2018 · 1 comment
Assignees

Comments

@PatrickLang
Copy link
Contributor

PatrickLang commented May 24, 2018

Is this an ISSUE or FEATURE REQUEST? (choose one): Issue


Which release version?: v1.0.3


Which component (CNI/IPAM/CNM/CNS): CNI


Which Operating System (Linux/Windows):

Windows Server version 1803


Which Orchestrator and version (e.g. Kubernetes, Docker)
Kubernetes

What happened:

168.x.x.x was first in the DNS server list. It can't resolve DNS within the k8s cluster.

What you expected to happen:

On Linux, 10.0.0.10 is the first and only server. This should be the same on Windows

/etc # cat resolv.conf
nameserver 10.0.0.10
search default.svc.cluster.local svc.cluster.local cluster.local lje1130gi5iehkdbexza4ptcba.xx.internal.cloudapp.net

How to reproduce it (as minimally and precisely as possible):
Deploy a Windows cluster using acs-engine v0.17

@sharmasushant
Copy link
Contributor

#155 fixes this

@sharmasushant sharmasushant self-assigned this May 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants