> ## Documentation Index
> Fetch the complete documentation index at: https://bunnynet-cb9733c2-support-migration.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# DNS Records
> Add, edit, and manage DNS records for your zone.
DNS records map domain names to IP addresses and other resources. Bunny DNS supports all standard record types and provides advanced features like weighted load balancing, smart routing, and health monitoring through record sets.
## Add a record
In the bunny.net dashboard, go to **DNS** and select your DNS Zone, then click **Add Record**.
Fill in the record details:
| Field | Description |
| ------------ | ------------------------------------------------------------------- |
| **Hostname** | The subdomain for this record. Leave empty for the root domain. |
| **Type** | The record type (A, AAAA, CNAME, MX, TXT, etc.) |
| **TTL** | Time to live. How long resolvers cache the record. |
| **Value** | The record value (IP address, hostname, or text depending on type). |
Expand **Advanced Settings** to configure additional options:
| Setting | Description |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Routing Weight** | Value between 0-100 that controls how often this record is returned relative to others in a record set. |
| **Monitoring** | Enable health monitoring to automatically remove offline records from responses. |
| **Smart Record Type** | Configure geographic or latency-based routing for A and AAAA records. |
| **Record Enabled** | Toggle to disable a record without deleting it. Disabled records remain visible but don't respond to queries. |
Click **Add Record** to save.
## Edit a record
To modify an existing record:
1. Locate the record in your DNS Zone
2. Click the **...** menu on the record row
3. Select **Edit**
4. Modify the record settings
5. Click **Save Record**
The record type cannot be changed when editing. Delete and recreate the record
if you need a different type.
## Delete a record
To remove a record:
1. Locate the record in your DNS Zone
2. Click the **...** menu on the record row
3. Select **Delete**
4. Click **Delete** to confirm
Deleting a record takes effect immediately. Make sure the record is no longer
needed before deleting.
## Quick edit TTL
You can change a record's TTL directly from the record list without opening the full edit dialog. Click the **TTL** value and select a new option:
* 15m
* 30m
* 1h
* 5h
* 12h
* 1D
## CDN Acceleration
CDN Acceleration routes traffic through Bunny CDN for improved performance and caching. Click the **CDN Acceleration** field in the record list to toggle it on or off.
When enabled:
* TTL automatically changes to **Auto**
* Click the settings icon to configure the connected Pull Zone
* Bunny CDN handles caching, optimization, and DDoS protection
## Record sets
A record set groups multiple DNS records of the same type that share the same name. Record sets enable advanced features like load balancing and failover.
### A and AAAA record sets
Record sets for A (IPv4) and AAAA (IPv6) records support:
* **Weighting**: Assign different weights to control how often each record is returned
* **Smart routing**: Route traffic based on geographic location or latency
* **Health monitoring**: Automatically remove unhealthy endpoints from responses
These features make A and AAAA record sets ideal for global load balancing and CDN configurations.
### Other record sets
For record types other than A and AAAA (such as TXT, CNAME, MX), all records in the set are returned together when queried.
## Smart records
A and AAAA records can be configured as Smart Records for dynamic routing based on user location.
### Geographic routing
Routes queries based on the end user's geographical location. The record closest to the user is returned. Location is determined using:
* Bunny DNS resolver location
* Query remote IP
* EDNS0 client subnet IP
### Latency routing
Routes queries based on estimated latency to bunny.net datacenter regions. Select the region closest to your server for accurate matching.
Latency routing may be more accurate than geographic routing since physical
distance doesn't always correlate with network latency.
## Load balancing
Bunny DNS supports DNS-based load balancing through weighted record sets and health monitoring.
### Weights
Every A and AAAA record has a **Routing Weight** (0-100) that controls how often it's returned relative to other records in the set.
For example, with two records where one has weight 100 and another has weight 50:
* First record returned approximately 66% of the time
* Second record returned approximately 33% of the time
If all records have equal weights, up to 3 records are randomly returned from the set.
### Health monitoring
Bunny DNS provides basic built-in monitoring for any A, AAAA, or CNAME record. When monitoring is enabled, each IP is tested every 30 seconds from a selection of 3 regions around the world. For a record to be detected as online, the monitored response must be successful.
The 30-second monitoring interval cannot currently be changed.
#### Monitoring types
Two monitoring types are available:
| Type | Description |
| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Ping** | Sends 4 ICMP ping packets to the monitored IP during each test from a region. At least one packet must return successfully within 2500ms for the test to pass. |
| **HTTP** | Sends HTTP requests to the configured IP on port 80. The request must complete within 10 seconds and return a non-5xx status code. Any other outcome (including a 5xx response) counts as a timeout. |
#### What happens when a record is offline
The behavior when a record is detected as offline depends on the record set:
* **Single-value records** continue to be returned regardless of health status.
* **Record sets** (multiple records sharing the same type and name) remove offline records from routing automatically.
* If **all records** in a set are offline, filtering is disabled to prevent false positives and all records continue to be returned.
Bunny DNS does not currently send alerts when an outage is detected. Alerting is planned for a future release.
## Wildcard records
A wildcard record (for example, `*.example.com`) is used to synthesize responses for any subdomain that does not have an explicit record of any type defined.
Bunny DNS intentionally deviates from [RFC 4592](https://datatracker.ietf.org/doc/html/rfc4592) when a wildcard interacts with an Empty Non-Terminal (ENT). An ENT is a name that has no records of its own but has descendants that do (for example, `b.example.com` is an ENT if only `a.b.example.com` exists). Per the RFC, queries for an ENT should return a NODATA response and the wildcard must not be expanded. Bunny DNS instead actively populates the response with the wildcard value, so queries for an ENT receive the wildcard record rather than an empty answer.
## Supported record types
### Standard records
| Type | Description |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **A** | Maps a domain to an IPv4 address |
| **AAAA** | Maps a domain to an IPv6 address |
| **CNAME** | Creates an alias pointing to another domain |
| **MX** | Specifies mail servers for the domain |
| **TXT** | Stores text data (SPF, DKIM, verification records) |
| **SRV** | Defines service locations (hostname, port, priority, weight) |
| **CAA** | Specifies which certificate authorities can issue certificates |
| **PTR** | Reverse DNS lookup |
| **NS** | Delegates a subdomain to other nameservers |
| **HTTPS** | HTTPS service binding record. Indicates that a service is available over HTTPS and can include connection parameters such as supported protocols and port numbers. |
| **SVCB** | General-purpose service binding record. Provides information about available services for a domain, including protocol and connection parameters. |
| **TLSA** | Associates a TLS certificate with a domain. Used with DANE to specify which certificate or CA should be trusted for a domain. |
Bunny DNS supports CNAME flattening on both **CNAME** and **Pull Zone (PZ)** records. When either is used at the zone apex (root domain), Bunny DNS automatically flattens it to A/AAAA records, so you can point a root domain directly at a Pull Zone.
### Bunny-specific records
| Type (UI label) | Description |
| ------------------ | ---------------------------------------------------------------- |
| **PZ** (Pull Zone) | Links a domain to a CDN Pull Zone for automatic CDN acceleration |
| **RDR** (Redirect) | URL redirect record. Redirects requests to another URL |
| **SCR** (Script) | Scriptable DNS responses using DNS script |