1. Each VPC has it's own DNS server. Each subnet also has it's DNS server
2. When you use VPC's DNS, it will first try to resolve the names, using the private hosted zones defined in Route53.
If not found, it will using the public DNS for name resolution
3. Buying Name and Hosting Name are two different things.
4. How DNS works:
There are dns servers for every domain.
It will start from last entry to the first entry. So if I want to resolve www.coverfox.com. It will first ask .com servers for
the entry corresponding to coverfox.com. In this case, it will find the godaddy server. Now godaddy has it's own nameservers
which routes ip address based on the records defined.
4. Every time, I define a public hosted zone in Route53, aws will assign specific set of name servers for name resolution for that zone.
5. If I want to use the config define in route53 to be used by godaddy which is used for name-resolution, in godaddy's config
page, I will replace godaddy's name server with the name servers that I got in the previous step. THIS IS HOW I AM ABLE TO CONNECT
AWS TO ROUTE53.

MY WORK:
1. Create a Application Load Balancer which will route the the public requests to the relevant server. This server can be private
2. Manage certicates for the load balancer
3. Create a public hosted zone that will route the requests to the load balacer's ip
4. Create a private hosted zone that will route the requessts to the private ip