anchor.diff:  
   == Deploy CoreDNS
   
  -The CoreDNS deployment relies on information that is specific to you cluster: CIDR of the kubernetes services and cluster domain.
  -
  -For kops, `coredns` can be deployed:
  +The CoreDNS deployment relies on information that is specific to you cluster: CIDR of the kubernetes services and cluster domain. CIDR is different based upon whether your cluster was created with kops or minikube.
  +
  +For kops, CoreDNS can be deployed using the following command:
   
   	$ kubectl create -f templates/coredns-kops.yaml
   	serviceaccount "coredns" created
  
positive.code: Address 1: 100.64.0.1
  ```
  
  The logs are updated to show the following output:
  
  	100.96.5.3 - [03/Nov/2017:01:35:35 +0000] "PTR IN 10.0.64.100.in-addr.arpa. udp 42 false 512" NXDOMAIN qr,rd,ra 101 1.664671ms
  	100.96.5.3 - [03/Nov/2017:01:35:35 +0000] "AAAA IN kubernetes.default. udp 36 false 512" NXDOMAIN qr,rd,ra 112 1.584983ms
  	100.96.5.3 - [03/Nov/2017:01:35:35 +0000] "AAAA IN kubernetes.default.default.svc.cluster.local. udp 62 false 512" NXDOMAIN qr,aa,rd,ra 115 127.264µs
  	100.96.5.3 - [03/Nov/2017:01:35:35 +0000] "AAAA IN kubernetes.default.svc.cluster.local. udp 54 false 512" NOERROR qr,aa,rd,ra 107 106.537µs
  	100.96.5.3 - [03/Nov/2017:01:35:35 +0000] "A IN kubernetes.default. udp 36 false 512" NXDOMAIN qr,rd,ra 112 523.381µs
  	100.96.5.3 - [03/Nov/2017:01:35:35 +0000] "A IN kubernetes.default.default.svc.cluster.local. udp 62 false 512" NXDOMAIN qr,aa,rd,ra 115 129.74µs
  	100.96.5.3 - [03/Nov/2017:01:35:35 +0000] "A IN kubernetes.default.svc.cluster.local. udp 54 false 512" NOERROR qr,aa,rd,ra 70 101.123µs
  	100.96.5.3 - [03/Nov/2017:01:35:35 +0000] "PTR IN 1.0.64.100.in-addr.arpa. udp 41 false 512" NXDOMAIN qr,rd,ra 100 1.500864ms
  
  The output shows that A records for `kubernetes.default.svc.cluster.local` are served by this instance.
  
  == Delete kube-dns deployment (optional)
  
  Kube-DNS pod is no longer required and thus can be deleted:
  
  	kubectl delete deployment kube-dns -n kube-system
  
  
negative.code: 	IP:                100.64.0.10
  	Port:              dns  53/UDP
  	TargetPort:        53/UDP
  	Endpoints:         100.96.6.2:53,100.96.7.2:53
  	Port:              dns-tcp  53/TCP
  	TargetPort:        53/TCP
  	Endpoints:         100.96.6.2:53,100.96.7.2:53
  	Port:              metrics  9153/TCP
  	TargetPort:        9153/TCP
  	Endpoints:         100.96.6.2:9153,100.96.7.2:9153
  	Session Affinity:  None
  	Events:            <none>
  
  The IP address of our CoreDNS pod should match the endpoint IPs in the kube-dns service:
  
  	$ kubectl get po -l k8s-app=coredns -n kube-system -o wide
  	NAME                       READY     STATUS    RESTARTS   AGE       IP           NODE
  	coredns-3986650266-1pxb6   1/1       Running   0          3m        100.96.6.2   ip-172-20-35-120.us-west-1.compute.internal
  	coredns-3986650266-rmfgm   1/1       Running   0          3m        100.96.7.2   ip-172-20-83-89.us-west-1.compute.internal
  
  Awesome, this fits nicely!
  
  To confirm, let's run the `nslookup` command again:
  
  ```
  $ kubectl exec -ti busybox -- nslookup kubernetes.default
  