title: Route 53 Subdomains and API Gateway
body: <p>I have a domain hosted through Route 53 called <em>foo.com</em> and all is good.  I have both NS and SOA records created in Route 53:</p>
  <pre><code>foo.com. NS
  ns-1609.awsdns-09.co.uk. 
  ns-431.awsdns-53.com. 
  ns-1071.awsdns-05.org. 
  ns-662.awsdns-18.net.
  
  foo.com. SOA
  ns-1609.awsdns-09.co.uk. awsdns-hostmaster.amazon.com.
  </code></pre>
  <p>We also segment our platforms by account.  So, we have an AWS subaccount that supports our DEV environment (following the AWS document: <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-routing-traffic-for-subdomains.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-routing-traffic-for-subdomains.html</a>).  So, within our foo.com hosted zone, we also have an entry:</p>
  <pre><code>devapi.foo.com. NS
  ns-3476.awsdns-09.co.uk. 
  ns-2341.awsdns-76.com. 
  ns-3245.awsdns-56.org. 
  ns-294.awsdns-67.net.
  </code></pre>
  <p>Within our AWS DEV account, we have a <em>devapi.foo.com</em> hosted zone with the exact same NS record:</p>
  <pre><code>devapi.foo.com. NS
  ns-3476.awsdns-09.co.uk. 
  ns-2341.awsdns-76.com. 
  ns-3245.awsdns-56.org. 
  ns-294.awsdns-67.net.
  </code></pre>
  <p>along with a SOA record and an A record that points at the DEV API Gateway:</p>
  <pre><code>devapi.foo.com. A  ALIAS f-8wdjr4hvgh.execute-api.us-east-2.amazonaws.com.
  </code></pre>
  <p>where <em>f-8wdjr4hvgh.execute-api.us-east-2.amazonaws.com.</em> is the domain name of the API Gateway.</p>
  <p>I have a custom domain mapping for <em>devapi.foo.com</em></p>
  <p>Unfortunately, in all of this, <em>devapi.foo.com</em> is not pingable/routable.  If you ping it, it returns an IP address but a Request timeout for icmp_seq* ...</p>
  <p>If I use <a href="https://www.whatsmydns.net/#A/" rel="nofollow noreferrer">https://www.whatsmydns.net/#A/</a> for <em>devapi.foo.com</em>, I get green check marks but I believe that all that is telling me is that the domain name is resolvable.</p>
  <p>Thoughts on what I am missing?</p>
  <p>Followup: The issue was with the Custom Domain Mapping and Base Path.</p>