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: 
  == Overview
  
  This guide will cover the how to attach a GlusterFS persistent volume to the Docker Registry.
  It is assumed that the docker registry service has already been started and the gluster volume has been created.
  
    
  === Prerequisites
  * The link:../install/docker_registry.html#deploy-registry[docker-registry] has been deployed *without*
  configuring storage.
  * A gluster volume exists and *glusterfs-fuse* is installed on schedulable nodes.
  * Definitions written for GlusterFS link:../persistent_storage/persistent_storage_glusterfs.html#creating-gluster-endpoints[endpoints and service],
  link:../persistent_storage/persistent_storage_glusterfs.html#gfs-creating-persistent-volume[persistent volume (*pv*)],
  and
  link:../../architecture/additional_concepts/storage.html#persistent-volume-claims[persistent volume claim (*pvc*)].
  ** For this guide, these will be:
  *** `gluster-endpoints-service.yaml`
  *** `gluster-endpoints.yaml`
  *** `gluster-pv.yaml`
  *** `gluster-pvc.yaml`
  * A user with the
  link:../../admin_guide/manage_authorization_policy.html#managing-role-bindings[*cluster-admin*] role binding.
  ** For this guide, that user is `admin`
  
  NOTE:  All `$ oc` commands are executed on the master node as the `admin` user
  
  
  [[create-gfs-pvc]]
  === Create the Gluster Persistent Volume
  
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[]
  ----
  