anchor.diff:  		<th>Note</th>
   	</tr>
   	<tr>
  -	  <td>CNAME</td>
  -	  <td>myapp</td>
  +	  <td>ALIAS</td>
  +	  <td>empty or @</td>
   	  <td>yourappname.cfapps.io.</td>
  -	  <td>Refer to your DNS provider documentation to determine whether the trailing `.` is required.</td>
  +	  <td>Refer to your DNS provider documentation to determine whether to use an empty or @ value for the Name entry.</td>
   	</tr>
   	</table>
   
  -**Root domain**: Some DNS providers support using an alternative custom record type, such as ANAME or ALIAS, for configuring custom zone apex domains. These domains are also known as root domains. ANAME and ALIAS records follow the pattern below:
  +### <a id='single-sub'></a>Map a Single Subdomain ###
  +
  +Use a DNS CNAME record to alias a multi-level custom subdomain.
  +
  + 1. Create the domain in Cloud Foundry and associate it with an organization.
  +
  +    The command below defines the custom domain `test.example.org` in the
  +	"test-org" organization:
  +
  +	<pre class="terminal">
  +	$ cf create-domain test-org test.example.org
  +	</pre>
  +
  + 1. Map the route to your app:
  +
  +    <pre class="terminal">
  +	$ cf map-route myapp test.example.org
  +	</pre>
  +
  + 1. Configure your custom domain with your DNS provider using a CNAME record.
  +
  +CNAME records follow the pattern illustrated below:
   
   <table border="1" class="nice" >
   	<tr>
  
positive.code: $ cf delete-domain example.org
  </pre>
  
  ## <a id='subdomain'></a>Key Facts About Subdomains ##
  
  In some cases, defining the subdomain portion of a route is optional. In
  generally, though, this segment of a route is required to ensure the route is
  unique.
  Note in particular that you _must_ define a subdomain in the following cases:
  
  
negative.code: A route is made up of a _subdomain_ (or host) and a _domain_ that you can
  specify when you push an application.
  
  ## <a id='domains'></a>Domains and Routes in Cloud Foundry ##
  
  A **domain** is a domain name like `acme.com` or `<%=vars.app_domain%>`. Domains can also be multi-level
  and contain sub-domains like the “store” in `store.acme.com`. In Cloud Foundry, domains are associated with orgs. Domain objects are not directly bound to apps.
  
  Cloud Foundry also supports custom domains. You can map a registered domain of your own to a space in Cloud Foundry.
  
  A **route**, based on a domain with an optional host as a prefix, may be associated with
  one or more applications. For example, `myapp` is the host and `<%=vars.app_domain%>` is the domain in the route `myapp.<%=vars.app_domain%>`. It is also possible to have a route that represents `<%=vars.app_domain%>` without a host. This type of route is
  known as a zone apex domain or a root domain. Routes are children of domains and are
  directly bound to apps in Cloud Foundry.
  
  A Cloud Foundry instance defines a default shared domain.
  Unless you specify a domain, `cf` uses the default shared domain in the route to
  your application.
  
  ## <a id='create-domains'></a>Use Your Custom Domain in Cloud Foundry ##
  
  There are three different models for using your own custom domain in Cloud Foundry. Select the procedure that corresponds with the type of domain you want to use.
  
  ### <a id='root'></a>Map a Root Domain ###
  
  Use a DNS ALIAS record to map a custom root domain to your app.
  
   1. Create the domain in Cloud Foundry and associate it with an organization.
  
      The command below defines the custom domain `example.org` in the
  	"test-org" organization:
  
  	<pre class="terminal">
  	$ cf create-domain test-org example.org
  	</pre>
  
   1. Map the route to your app:
  
      <pre class="terminal">
  	$ cf map-route myapp example.org
  	</pre>
  
   1. Configure your custom root domain with your DNS provider using an ALIAS record.
  
  ALIAS records follow the pattern illustrated below:
  
  <table border="1" class="nice" >
  	<tr>
  