Record sets in DNS are essential for managing multiple records of the same type associated with the same name. This document outlines how record sets function within Bunny DNS, detailing their usage, special handling principles, and the options available for different types of record sets.
What are record sets?
A record set groups multiple DNS records of the same type that share the same name. In the Bunny DNS control panel, these sets are displayed together under a main record, facilitating easier management and application of special configurations. Record sets enhance the DNS management experience by providing advanced features such as load balancing, smart routing, and health monitoring.
Features of record sets
When a record set is created, the DNS record table in the Bunny DNS control panel is updated to include additional options that aid in the precise control and configuration of the records within the set.
A and AAAA record sets
Record sets composed of A (IPv4 address) and AAAA (IPv6 address) records are designed to support advanced DNS functionalities:
- Weighting: Assigns different weights to records within the set, influencing the frequency with which they are served in response to queries.
- Smart routing: Dynamically routes traffic based on various criteria, such as geographic location, server performance, and network conditions.
- Health monitoring: Automatically checks the health of the endpoints associated with the records and adjusts routing accordingly.
These features make A and AAAA record sets suitable for use as a global Content Delivery Network (CDN) or a DNS-based load balancer.
NOTE: For detailed insights into these functionalities, refer to Understanding Bunny DNS Load Balancer and Understanding Bunny DNS Smart Records.
When CDN Proxy is enabled on an A or AAAA record set, Bunny CDN leverages the full configuration range of the set, optimizing content delivery and load balancing.
Other record sets
For record types other than A and AAAA, such as TXT, CNAME, MX, etc., Bunny DNS adopts a simpler approach. When these record sets are queried, all records within the set and their respective values are returned. This straightforward handling ensures clarity and consistency in the DNS responses.
For instance, a query to hello.bunny.dev with two TXT records in its set would result in both ’hello’ and ’world’ TXT records being returned.