From 3ebef7eeceb9a93f19be6947961c2dd9738d9a5d Mon Sep 17 00:00:00 2001 From: Bilgin Ibryam Date: Fri, 9 Dec 2016 08:49:26 +0000 Subject: [PATCH] Fixed typos --- docs/admin/dns.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/admin/dns.md b/docs/admin/dns.md index d75acfa093..5e9d55f822 100644 --- a/docs/admin/dns.md +++ b/docs/admin/dns.md @@ -70,7 +70,7 @@ is no longer supported. When enabled, pods are assigned a DNS A record in the form of `pod-ip-address.my-namespace.pod.cluster.local`. -For example, a pod with ip `1.2.3.4` in the namespace `default` with a dns name of `cluster.local` would have an entry: `1-2-3-4.default.pod.cluster.local`. +For example, a pod with ip `1.2.3.4` in the namespace `default` with a DNS name of `cluster.local` would have an entry: `1-2-3-4.default.pod.cluster.local`. #### A Records and hostname based on Pod's hostname and subdomain fields @@ -171,7 +171,7 @@ busybox 1/1 Running 0 Once that pod is running, you can exec nslookup in that environment: ``` -kubectl exec busybox -- nslookup kubernetes.default +kubectl exec -ti busybox -- nslookup kubernetes.default ``` You should see something like: @@ -194,10 +194,10 @@ If the nslookup command fails, check the following: Take a look inside the resolv.conf file. (See "Inheriting DNS from the node" and "Known issues" below for more information) ``` -cat /etc/resolv.conf +kubectl exec busybox cat /etc/resolv.conf ``` -Verify that the search path and name server are set up like the following (note that seach path may vary for different cloud providers): +Verify that the search path and name server are set up like the following (note that search path may vary for different cloud providers): ``` search default.svc.cluster.local svc.cluster.local cluster.local google.internal c.gce_project_id.internal @@ -210,7 +210,7 @@ options ndots:5 Errors such as the following indicate a problem with the kube-dns add-on or associated Services: ``` -$ kubectl exec busybox -- nslookup kubernetes.default +$ kubectl exec -ti busybox -- nslookup kubernetes.default Server: 10.0.0.10 Address 1: 10.0.0.10 @@ -220,7 +220,7 @@ nslookup: can't resolve 'kubernetes.default' or ``` -$ kubectl exec busybox -- nslookup kubernetes.default +$ kubectl exec -ti busybox -- nslookup kubernetes.default Server: 10.0.0.10 Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local @@ -244,7 +244,7 @@ kube-dns-v19-ezo1y 3/3 Running 0 ... ``` -If you see that no pod is running or that the pod has failed/completed, the dns add-on may not be deployed by default in your current environment and you will have to deploy it manually. +If you see that no pod is running or that the pod has failed/completed, the DNS add-on may not be deployed by default in your current environment and you will have to deploy it manually. #### Check for Errors in the DNS pod @@ -258,7 +258,7 @@ kubectl logs --namespace=kube-system $(kubectl get pods --namespace=kube-system See if there is any suspicious log. W, E, F letter at the beginning represent Warning, Error and Failure. Please search for entries that have these as the logging level and use [kubernetes issues](https://github.com/kubernetes/kubernetes/issues) to report unexpected errors. -#### Is dns service up? +#### Is DNS service up? Verify that the DNS service is up by using the `kubectl get service` command. @@ -277,7 +277,7 @@ kube-dns 10.0.0.10 53/UDP,53/TCP 1h If you have created the service or in the case it should be created by default but it does not appear, see this [debugging services page](http://kubernetes.io/docs/user-guide/debugging-services/) for more information. -#### Are dns endpoints exposed? +#### Are DNS endpoints exposed? You can verify that dns endpoints are exposed by using the `kubectl get endpoints` command. @@ -348,7 +348,7 @@ some of those settings will be lost. As a partial workaround, the node can run `dnsmasq` which will provide more `nameserver` entries, but not more `search` entries. You can also use kubelet's `--resolv-conf` flag. -If you are using Alpine version 3.3 or earlier as your base image, dns may not +If you are using Alpine version 3.3 or earlier as your base image, DNS may not work properly owing to a known issue with Alpine. Check [here](https://github.com/kubernetes/kubernetes/issues/30215) for more information.