> For the complete documentation index, see [llms.txt](https://docs.vngcloud.vn/vng-cloud-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vngcloud.vn/vng-cloud-document/vdns/features.md).

# Features

### A Powerful DNS Solution for Private Cloud Infrastructure

vDNS is a DNS service specifically designed for Private Cloud environments on GreenNode, providing secure, flexible, and efficient domain management and resolution within Virtual Private Clouds (VPCs).

### Core Features of vDNS

#### Enable Private DNS Server for VPCs

This feature allows you to enable a dedicated DNS server within your VPC. It ensures that virtual machines (VMs) inside the VPC can resolve domain names privately without using the public internet.

Enabling the Private DNS Server will create one or more dedicated IP addresses for the DNS server within the VPC. These addresses will be automatically configured for VMs in the VPC via DHCP.

This is a prerequisite step for using other vDNS features within the VPC.

{% hint style="info" %}
**Important Note:** Enabling Private DNS will modify the DHCP Option Set of VMs in the network. Therefore, after enabling the feature, you need to update DHCP on the VMs so they can receive the new DNS configuration. Please refer to the DHCP update guide [here.](/vng-cloud-document/vserver/compute-hcm03-1a/vpc/dhcp-options-sets.md)
{% endhint %}

### Create Hosted Zone

A Hosted Zone is a container for DNS records of a specific domain (for example: `example.com`).

vDNS allows you to create two types of Hosted Zones:

* **Public Hosted Zone:** Used for public domains that can be resolved from the internet. *(Currently not supported in this version.)*
* **Private Hosted Zone:** Used for internal domains that can only be resolved within associated VPCs.

#### Important Point

When creating a Private Hosted Zone, vDNS only allows association with VPCs that have the Private DNS Server feature enabled. This ensures network security and isolation.

### Edit Hosted Zone

#### Attach or Detach VPCs from a Hosted Zone

After creating a Hosted Zone (especially a Private Hosted Zone), you can easily modify it by adding or removing associated VPCs.

This allows you to control the resolution scope of a domain. For example, you can allow an internal domain to be resolved by multiple VPCs or restrict it to a single VPC only.

### Create Records

Supports 6 record types and 3 routing policies.

vDNS fully supports common DNS record types:

* **A:** Maps a domain name to an IPv4 address.
* **CNAME:** Creates an alias for another domain name.
* **MX:** Specifies mail servers.
* **SRV:** Specifies the location of specific services.
* **TXT:** Stores arbitrary text.
* **PTR:** Performs reverse DNS lookup, mapping an IP address back to a domain name.

vDNS also provides flexible routing policies:

* **Simple Routing:** Simple routing that returns a set of resources in order.
* **Geolocation Routing:** Routes traffic based on the user’s geographic location.
* **Weighted Routing (with Sticky Session):** Distributes traffic based on weights while maintaining session persistence.

*(Terraform integration for vDNS is currently not supported.)*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.vngcloud.vn/vng-cloud-document/vdns/features.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.