anchor.diff:  	IP:                100.64.0.10
   	Port:              dns  53/UDP
   	TargetPort:        53/UDP
  -	Endpoints:         100.96.6.2:53
  +	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
  +	Endpoints:         100.96.6.2:53,100.96.7.2:53
   	Port:              metrics  9153/TCP
   	TargetPort:        9153/TCP
  -	Endpoints:         100.96.6.2:9153
  +	Endpoints:         100.96.6.2:9153,100.96.7.2:9153
   	Session Affinity:  None
   	Events:            <none>
   
  -If all went correct, the IP of our CoreDNS pod should match the endpoint IPs in the kube-dns service:
  +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-2rt2s   1/1       Running   0          2m        100.96.7.2   ip-172-20-84-184.us-west-1.compute.internal
  +	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 `nslookup` command from the <<Status Quo>> section:
  +To confirm, let's run the `nslookup` command again:
   
   ```
   $ kubectl exec -ti busybox -- nslookup kubernetes.default
  
positive.code: ```
  
  The output shows that the `kube-dns` service answered the request and the `kubernetes` service can be found at `100.64.01`.
  
  Lets look at the `resolv.conf`:
  
  
negative.code: 	Session Affinity:  None
  	Events:            <none>
  
  Let's look at the list of Deployments:
  
  	$ kubectl get deployments -n kube-system -l k8s-app=kube-dns
  	NAME       DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
  	kube-dns   2         2         2            2           8m
  
  The output shows that 2 replicas of Kube-DNS pods are running.
  
  Let's get more details about the pods:
  
  	$ kubectl get pods -n kube-system -l k8s-app=kube-dns 
  	NAME                        READY     STATUS    RESTARTS   AGE
  	kube-dns-1311260920-d8bkh   3/3       Running   0          8m
  	kube-dns-1311260920-v06zv   3/3       Running   0          7m
  
  Get logs from one of the pods:
  
  	kubectl logs -n kube-system kube-dns-1311260920-d8bkh --container kubedns
  
  To validate that the current DNS setup is working we first have to deploy a `busybox` pod:
  
  	$ kubectl create -f templates/busybox.yaml
  