Help Center/ Domain Name Service/ User Guide (Paris Region) / Overview/ Public Domain Name Resolution
Updated on 2024-03-14 GMT+08:00
View PDF
Share

Public Domain Name Resolution

Public Zone

A public zone contains information about how a domain name and its subdomains are translated into IP addresses for routing traffic over the Internet. Public zones allow end users to access your website or application over the Internet using your domain name.

Accessing a Website Using a Domain Name

To make your website accessible on the Internet through a domain name, perform the following steps:

  1. Register your domain name with a domain name registrar so that end users can use the domain name to access your website.
  2. Set up your website.

    Purchase cloud resources.

  3. Configure the DNS service to route Internet traffic for your domain name.

    Create a public zone to host the domain name on the DNS service and add a record set to map the domain name to the EIP of the server where the website is set up.

    For details, see Routing Internet Traffic to a Website.

After you finish the above steps, end users will be able to access your website over the Internet with the registered domain name and its subdomains.

Figure 1 How DNS routes Internet traffic to a website
  • Phase 1 shows how DNS resolves your domain name.
  • Phase 2 shows how the web page is returned to the user.

Public domain name resolution depends on the DNS hierarchy. The following describes the hierarchies of domain names and how domain names are resolved.

DNS Hierarchy

Domain names are hierarchical, and domain name resolution is a recursive lookup process. The following uses example.com to describe the hierarchies in domain names.

  • Root domain

    A dot (.) is the designation for the root domain.

    A fully qualified domain name (FQDN) ends with a dot (example.com.). When you enter a domain name (example.com) in the browser, the DNS system will automatically add a dot in the end.

    Root domain names are resolved by root DNS servers that hold the addresses of top-level DNS servers.

  • Top-level domain

    Below the root domain are top-level domains, which are categorized into two types:

    • Generic top-level domain (gTLD), such as .com, .net, .org, and .top
    • Country code top-level domain (ccTLD), such as .cn, .uk, and .de

    Top-level domains are resolved by top-level DNS servers that hold the addresses of second-level DNS servers. For example, the top-level DNS server of .com saves the addresses of all DNS servers of second-level domain names that end with .com.

  • Second-level domain

    Second-level domains (such as example.com) are subdomains of top-level domains and are resolved by second-level DNS servers, which provide authoritative domain name resolution services.

    For example, if you purchase example.com from a domain name registrar and set a DNS server for the domain name, the DNS server will provide authoritative resolution for example.com, and its address will be recorded by all top-level DNS servers.

    If you host domain names on DNS, authoritative DNS servers will be provided for the domain names.

Domain Name Resolution

Figure 2 shows the process for accessing a website using the domain name www.example.com.

Figure 2 Domain name resolution
  1. An end user enters www.example.com in the address box of a browser.
  2. The request for querying domain name www.example.com is routed to the local DNS server.

    Local DNS servers are usually provided by the Internet service provider to cache domain name information and perform recursive lookup.

  3. If the local DNS server does not find any records in the cache, it routes the request for www.example.com to the root DNS server.
  4. The root DNS server returns the DNS server address of .com (because the domain name suffix is .com) to the local DNS server.
  5. The local DNS server sends the request to the top-level DNS server of .com.
  6. The top-level DNS server of .com returns the address of the authoritative DNS server which provides authoritative records for example.com.
  7. The local DNS server sends the request to the authoritative DNS server of example.com.

    If you have hosted www.example.com on the DNS service and configure the name servers provided by the DNS service, these name servers will provide authoritative DNS for the domain name.

  8. The authoritative DNS server returns the IP address mapped to www.example.com to the local DNS server.
  9. The local DNS server returns the IP address to the web browser.
  10. The web browser accesses the web server with the IP address.
  11. The web server returns the web page to the browser.
  12. The end user views the web page using the browser.

For details, see Routing Internet Traffic to a Website.

Parent topic: Overview