anchor.diff:  
    * configuring dhcp to include the local IP address in /etc/resolv.conf upon boot
    * configuring dnsmasq
  - * configuring openshift dns to listen on another port
  -
  -In my dev setup, I have openshifts DNS listening on 127.0.0.1:8053.
  + * configuring OpenShift dns to listen on another port
  +
  +In my dev setup, I have OpenShifts DNS listening on 127.0.0.1:8053.
   I have my dnsmasq listening on the local IP address 192.168.0.109:53
   
   Therefore in my /etc/dhcp/dhclient.conf I have this config:
  
positive.code: = Openshift Installation, Examples, and Tips - Crunchy Containers
  Crunchy Data Solutions, Inc.
  v1.4.1, {docdate}
  :title-logo-image: image:crunchy_logo.png["CrunchyData Logo",align="center",scaledwidth="80%"]
  
  == Openshift Installation
  
  === Install Openshift Enterprise
  
  See the OSE installation guide for details on how to install
  OSE on your host.  The main instructions are here:
  
  https://docs.openshift.com/enterprise/3.2/install_config/install/index.html
  
  === Install Openshift Origin
  
  The easiest way to get Openshift Origin up and running is found here:
  https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md
  
  == Examples for the Openshift Environment
  The examples/openshift directory containers examples for
  running the Crunchy containers in an Openshift environment.
  
  The examples are explained below.
  
  
negative.code: 
  === Tip 14: DNS host entry and DeploymentConfig
  
  If your OpenShift environment can not resolve your hostname via
  a DNS server (external to OpenShift!), you will get errors when trying
  to create a DeploymentConfig.  So, you can either install dnsmasq
  and reconfigure OpenShift for that, or, you can run a DNS server
  on another host and add the OpenShift host entry to that DNS server.  I
  use the skybridge2 Docker container for this purpose.  You have
  to remember to adjust your /etc/resolv.conf to specify this new DNS
  server.
  