DNS resolution not working with vm-driver none

[saivarunr]

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.30.0

• OS (e.g. from /etc/os-release): Ubuntu 16.04.4 LTS (Xenial Xerus)
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): none
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
• Install tools:
• Others:
  The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):

minikube version
echo "";
echo "OS:";
cat /etc/os-release
echo "";
echo "VM driver:"; 
grep DriverName ~/.minikube/machines/minikube/config.json
echo "";
echo "ISO version";
grep -i ISO ~/.minikube/machines/minikube/config.json

What happened:
service name resolution is un-stable, once it is resolved, after a while it won't
What you expected to happen:
service name should be resolved.
How to reproduce it (as minimally and precisely as possible):
Create a pod and expose a service.
Poll to the above service from another pod.
Output of minikube logs (if applicable):

Anything else do we need to know:

[hach-que]

Still an issue on 0.32.0.

[blind3dd]

yup, found out yesterday that Introduced KubeAdm change with resolv.conf doesn't solve the issue here and still the manual change in /etc/hosts file had to be done inside of a pod with service name and service ip like (redis-server - ip)
I'll put more info after updating kubectl to the newest version.

[davidgarciaMontreal]

This is working for me on version 1.0.0. i logged into a pod and the dns resolution does work.
Why is this ticket still open?

sudo rm /etc/resolv.conf
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

vagrant@dhost:~/poc-bob/vagrant$ minikube version
minikube version: v1.0.0
sudo minikube start --vm-driver=none

[saivarunr]

Minikube version it didn't work for is : v0.30.0

[tstromberg]

Thanks for the update! I'm marking this as obsolete.

[schollii]

@tstromberg I'm facing this issue with minikube v1.0.0 running in ubuntu vm (so vm-driver=none), ie if I shell into a pod I can connect to another pod by cluster IP of the associated service but not by name of the service. What is the solution, not clear from the above discussion.

[schollii]

Actually just saw #3511 (comment), trying it....

Update: that worked. I had to delete the cluster first. After the restart with given flag, the core-dns pods were running fine and dns resolution on services works.

[blind3dd]

you can always put service names and their matching pod ip to all the containers /etc/hosts files :-) pb

…

On Thu, May 16, 2019, 5:13 PM schollii ***@***.***> wrote: Actually just saw #3511 (comment) <#3511 (comment)>, trying it — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3375?email_source=notifications&email_token=AEH46ZQKYGJLB7CSPDVZ2ZDPVV23DA5CNFSM4GHATFF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVSEEGI#issuecomment-493109785>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEH46ZVVAGADYGD4DM664B3PVV23DANCNFSM4GHATFFQ> .