anchor.diff:  ```
   
   The output shows that the `kube-dns` service answered the request and the `kubernetes` service can be found at `100.64.01`.
  +
  +Let's look at the logs from one of the pods:
  +
  +	$ kubectl logs -n kube-system kube-dns-1311260920-v06zv --container sidecar
  +	ERROR: logging before flag.Parse: I1103 01:55:35.006798       1 main.go:48] Version v1.14.4-2-g5584e04
  +	ERROR: logging before flag.Parse: I1103 01:55:35.006838       1 server.go:45] Starting server (options {DnsMasqPort:53 DnsMasqAddr:127.0.0.1 DnsMasqPollIntervalMs:5000 Probes:[{Label:kubedns Server:127.0.0.1:10053 Name:kubernetes.default.svc.cluster.local. Interval:5s Type:1} {Label:dnsmasq Server:127.0.0.1:53 Name:kubernetes.default.svc.cluster.local. Interval:5s Type:1}] PrometheusAddr:0.0.0.0 PrometheusPort:10054 PrometheusPath:/metrics PrometheusNamespace:kubedns})
  +	ERROR: logging before flag.Parse: I1103 01:55:35.006926       1 dnsprobe.go:75] Starting dnsProbe {Label:kubedns Server:127.0.0.1:10053 Name:kubernetes.default.svc.cluster.local. Interval:5s Type:1}
  +	ERROR: logging before flag.Parse: I1103 01:55:35.007006       1 dnsprobe.go:75] Starting dnsProbe {Label:dnsmasq Server:127.0.0.1:53 Name:kubernetes.default.svc.cluster.local. Interval:5s Type:1}
  +
  +It shows that `kubernetes.default.svc.cluster.local` was resolved.
  +
  +And, now logs from the other pod:
  +
  +	coredns $ kubectl logs -n kube-system kube-dns-1311260920-d8bkh --container sidecar
  +	ERROR: logging before flag.Parse: I1103 01:55:33.917264       1 main.go:48] Version v1.14.4-2-g5584e04
  +	ERROR: logging before flag.Parse: I1103 01:55:33.917308       1 server.go:45] Starting server (options {DnsMasqPort:53 DnsMasqAddr:127.0.0.1 DnsMasqPollIntervalMs:5000 Probes:[{Label:kubedns Server:127.0.0.1:10053 Name:kubernetes.default.svc.cluster.local. Interval:5s Type:1} {Label:dnsmasq Server:127.0.0.1:53 Name:kubernetes.default.svc.cluster.local. Interval:5s Type:1}] PrometheusAddr:0.0.0.0 PrometheusPort:10054 PrometheusPath:/metrics PrometheusNamespace:kubedns})
  +	ERROR: logging before flag.Parse: I1103 01:55:33.917386       1 dnsprobe.go:75] Starting dnsProbe {Label:kubedns Server:127.0.0.1:10053 Name:kubernetes.default.svc.cluster.local. Interval:5s Type:1}
  +	ERROR: logging before flag.Parse: I1103 01:55:33.917455       1 dnsprobe.go:75] Starting dnsProbe {Label:dnsmasq Server:127.0.0.1:53 Name:kubernetes.default.svc.cluster.local. Interval:5s Type:1}
  +
  +And this shows a similar output.
   
   Lets look at the `resolv.conf`:
   
  
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: 
  == Deploy CoreDNS
  
  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
  