anchor.diff:  ----
   ====
   
  -With these settings, `dnsmasq` will pull from the `/etc/hosts` file on the master node.
  -Add the appropriate hostnames and IPs for all necessary hosts.
  +With these settings, *dnsmasq* will pull from the *_/etc/hosts_* file on the
  +master node.
   
  -In *master-config.yaml*, change `bindAddress` to:
  +Add the appropriate host names and IPs for all necessary hosts.
  +
  +In *_master-config.yaml_*, change `*bindAddress*` to:
   ====
   ----
   dnsConfig:
  
positive.code: gluster-claim   <none>    Bound     gluster-pv   1Gi        RWX           24s
  ----
  
  
  
  NOTE: If either the *pvc* or *pv* failed to create or the pvc failed to bind, refer back to the
  link:../persistent_storage/persistent_storage_glusterfs.html[GlusterFS Persistent Storage] guide.
  *Do not* proceed until they initialize and the pvc status is `Bound`
  
  [[attach-pvc-to-reg]]
  === Attach the PVC to the Docker Registry
  
  Before moving forward, ensure that the docker-registry service is running.
  
  ----
  $ oc get svc
  
negative.code: ----
  ====
  
  When pods are created, they receive a copy of *_/etc/resolv.conf_*, which
  typically contains only the master DNS server so they can resolve external DNS
  requests. To enable internal DNS resolution, insert the *dnsmasq* server at the
  top of the server list. This way, *dnsmasq* will attempt to resolve requests
  internally first.
  
  In *_/etc/resolv.conf_* all scheduled nodes:
  
  ====
  ----
  nameserver 192.168.1.100  <1>
  nameserver 192.168.1.1    <2>
  ----
  <1> Add the internal DNS server.
  <2> Pre-existing external DNS server.
  ====
  
  Once the configurations are changed, restart the {product-title} master and
  *dnsmasq* services.
  
  ifdef::openshift-enterprise[]
  ----
  