Discussions

Dear ControlD Team,

I am writing to suggest an enhancement to the domain redirection feature within ControlD's custom rules.

Currently, when using ControlD's custom rules to redirect a domain, it's only possible to specify a single A or CNAME record. While this is functional, it presents a limitation in certain scenarios.

My suggestion is to enhance this functionality to allow users to configure multiple A or CNAME records for a single domain. This would mean that instead of being restricted to just one target IP address (A record) or one canonical name (CNAME record), users could specify a list of them.

This enhancement is crucial for scenarios requiring redundancy, load balancing, and mimicking real-world DNS behavior. In real-world DNS scenarios, it's common for domains to resolve to multiple A or CNAME records. This is often used for redundancy, load balancing, and geographic distribution. For example, many large online services utilize multiple A records to distribute traffic across different servers and ensure high availability. Similarly, some domains might use multiple CNAME records for various reasons related to service architecture and management.

By allowing users to configure multiple A or CNAME records in ControlD's custom rules, we could achieve:

• Increased Flexibility: Users could create more complex and realistic redirection rules.
• Improved Redundancy: If one of the target IPs or canonical names becomes unavailable, the redirection could still function through the other records.
• Enhanced Realism: It would allow users to more accurately replicate the behavior of actual DNS records, which often contain multiple A or CNAME entries.

In conclusion, adding support for multiple A or CNAME records for domain redirection would be a valuable improvement, significantly enhancing the flexibility and power of ControlD's custom rule feature. This would allow for more sophisticated and robust custom configurations.

Thank you for considering this suggestion.