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

Commit

Permalink
Merge pull request #852 from ybart/patch-2
Browse files Browse the repository at this point in the history
fix(minikube/dns): Add precisions about dnsmasq
  • Loading branch information
Matthew Fisher authored Aug 10, 2017
2 parents 4bb1f54 + 5c2ed7c commit 56e27a2
Showing 1 changed file with 12 additions and 1 deletion.
13 changes: 12 additions & 1 deletion src/quickstart/provider/minikube/dns.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ something-random.192.168.99.100.nip.io has address 192.168.99.100

### Using DNSMasq

If you `nip.io` is working for you, you can skip this section, and proceed to verify the hostname.
If `nip.io` is working for you, you can skip this section, and proceed to verify the hostname.

If you prefer not to use `nip.io` or cannot (because your DNS provider might have blocked it), you can use `dnsmasq` on Linux and macOS or `Acrylic` on Windows.

Expand All @@ -57,6 +57,17 @@ $ echo nameserver 127.0.0.1 | sudo tee /etc/resolver/minikube
$ sudo killall -HUP mDNSResponder
```

You may need to ensure that the `dnsmasq` service at 127.0.0.1 is listed as a DNS server for your network connection. You may check this using the following command:

```sh
$ scutil --dns | grep minikube -B 1 -A 3
resolver #8
domain : minikube
nameserver[0] : 127.0.0.1
flags : Request A records, Request AAAA records
reach : Reachable, Local Address, Directly Reachable Address
```

To verify the hostname, you will need to use `deis.minikube` as hostname instead of `deis.192.168.99.100.nip.io` in the next section. We will also use it in the next step.

### Verify the hostname
Expand Down

0 comments on commit 56e27a2

Please sign in to comment.