We pick d.root-servers.net, one of the 13 root servers (1), and ask it about siliconvalley.citysearch.com and learn that com is delegated to 13 name servers (2), so we ask d.gtld-servers.net where we learn that citysearch.com is delegated to three name servers, including ns3.citygrid.com (3), so we ask that one where we see a CNAME from siliconvalley.citysearch.com to cspxy-vip.citysearch.com, so we have to start all over again. We already know that ns3.citygrid.com is authoritative for citysearch.com (4) and ask it about cspxy-vip.citysearch.com and see a second CNAME from cspxy-vip.citysearch.com to cspxy-vip.aws1.citysearch.com. We start over for the third time and we already know that ns1.citygrid.com is authoritative for citysearch.com (5) and ask it about cspxy-vip.aws1.citysearch.com and see yet another CNAME from cspxy-vip.aws1.citysearch.com to aws1pvipcsp1.csprod.ctgrd.com. We have yet again to start all over and we already know that i.gtld-servers.net is authoritative for com (6) and ask it about aws1pvipcsp1.csprod.ctgrd.com and learn that ctgrd.com is delegated to three name servers (7), so we ask ns2.citygrid.com where we learn that csprod.ctgrd.com is delegated to four name servers, including ns-639.awsdns-15.net (8), so we ask that one and see yet another CNAME from aws1pvipcsp1.csprod.ctgrd.com to dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com. We have yet again to start all over and we already know that e.gtld-servers.net is authoritative for com (9) and ask it about dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com and learn that amazonaws.com is delegated to ten name servers (10), so we ask u3.amazonaws.com where we learn that us-east-1.elb.amazonaws.com is delegated to eight name servers, including ns-947.amazonaws.com (11), so we ask that one and get the following answer:
