# Domains

## Introduction to Domains

A domain is like an easy-to-remember address for a website on the internet, such as `dAppling.network`.

### DNS: The Domain Name System

DNS translates human-friendly domain names to computer-readable IP addresses, a process known as DNS resolution.

### The DNS Query Process

Here's how a DNS query unfolds:

1. **User's Request:** Enter a domain like `example.dAppling.network` in your browser.
2. **Recursive Resolver:** If the IP is not cached, the browser queries a recursive resolver.
3. **DNS Server Hierarchy:** The resolver consults a series of DNS servers.
4. **IP Address Retrieval:** The authoritative nameserver provides the IP address.

### DNS Network Hierarchy

DNS is structured hierarchically with root, TLD, and authoritative nameservers.

### Efficiency in DNS Queries

DNS queries are optimized for speed, with caching mechanisms in browsers and resolvers.

### Developer Perspective: Setting Up a Site on dAppling.network

Deploying a project on dAppling.network requires configuring DNS settings to point your domain to the correct IP address.

### Configuring DNS Settings on dAppling.network

Your Dashboard provides guidance on setting various DNS records.

### Key DNS Records and Their Functions

* **CNAME (Canonical Name)**
* **A (Address)**
* **NS (Nameserver)**
* **MX (Mail Exchange)**

### SSL Certificates

SSL Certificates ensure a secure connection from your domain to your website.

***

:cactus:*Fun Fact: Cactus can perform photosynthesis at night, unlike most plants, which only do so during the day.*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dappling.network/domains.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.