anchor.diff:  link:../core_objects/kubernetes_model.html#service[services], such as frontend
   and backend services for use with multiple pods, in order for the frontend pods
   to communicate with the backend services, environment variables are created for
  -username, service-ip, etc. If the service is deleted and recreated, a new IP
  -address can be assigned to the service, and requires the frontend pods to be
  +user names, service IP, and more. If the service is deleted and recreated, a new
  +IP address can be assigned to the service, and requires the frontend pods to be
   recreated in order to pick up the updated values for the service IP environment
   variable. Additionally, the backend service has to be created before any of the
   frontend pods to ensure that the service IP is generated properly and that it
   can be provided to the frontend pods as an environment variable.
   
  -For this reason, OpenShift has an built-in DNS so that the services can be
  +For this reason, OpenShift has a built-in DNS so that the services can be
   reached by the service DNS as well as the service IP/port. OpenShift supports
   split DNS by running link:https://github.com/skynetservices/skydns[SkyDNS] on the master that answers DNS queries for
   services. The master listens to port 53 by default.
  
positive.code: This prevents having to restart frontend pods in order to pick up new services,
  which creates a new IP for the service. This also removes the need to use
  environment variables, as pods can use the service DNS. Also, as the DNS does not change, you can reference database services as
  "db.local" in config files. Wildcard lookups are also supported, as any lookups
  resolve to the service IP, and removes the need to create the backend service
  before any of the frontend pods, since the service name (and hence DNS) is
  established upfront.
  
negative.code: 
  On a node host, each Docker container's nameserver has the master added to the
  front, and the default search domain for the container will be
  `._<pod_namespace>_.local`. The container will then direct any nameserver
  queries to the master before any other nameservers on the node, which is the
  default Docker behavior. The master will answer queries on the `.local` domain
  that have the following form:
  
  ----
  