Feature Request: Duplicate DNS Record Alert System with "Ignore" Functionality #1

New issue

Closed

opened 2026-04-09 10:35:59 -03:00 by whillavila · 1 comment

whillavila commented

2026-04-09 10:35:59 -03:00

(Migrated from github.com)

Proposed Solution
I suggest implementing a real-time (or pre-save) alert system within the DNS management interface. When the system detects a record with the same Name, Type, and Value (or other logic depending on the specific record type), it should trigger a warning.

Key Features
Visual Alert: A warning icon or a banner next to the duplicated entries.

Contextual Information: A brief tooltip explaining why the record is flagged as a duplicate.

"Ignore" Action: A button or link within the alert that allows the user to dismiss the warning for that specific instance. This is crucial for certain configurations where duplicates might be intentional (e.g., Round Robin DNS).

User Interface (Mockup/Description)
Detection: As the user types or after a record is added, the UI highlights the row.

Notification: An alert box appears: "Warning: Duplicate record detected."

Action: Two buttons: [Review Changes] and [Ignore Warning].

Persistent State: If "Ignore" is clicked, the warning disappears for the current session (or is stored in the record metadata).

Additional Context
Preventing human error at the interface level will significantly reduce support tickets related to "broken" DNS configurations that are actually just results of accidental duplication.

Problem Statement Currently, the interface does not notify users when duplicate DNS records are created. This can lead to configuration conflicts, unexpected routing behavior, and general clutter in the zone management view. Users need a visual cue to identify and resolve these redundancies quickly. Proposed Solution I suggest implementing a real-time (or pre-save) alert system within the DNS management interface. When the system detects a record with the same Name, Type, and Value (or other logic depending on the specific record type), it should trigger a warning. Key Features Visual Alert: A warning icon or a banner next to the duplicated entries. Contextual Information: A brief tooltip explaining why the record is flagged as a duplicate. "Ignore" Action: A button or link within the alert that allows the user to dismiss the warning for that specific instance. This is crucial for certain configurations where duplicates might be intentional (e.g., Round Robin DNS). User Interface (Mockup/Description) Detection: As the user types or after a record is added, the UI highlights the row. Notification: An alert box appears: "Warning: Duplicate record detected." Action: Two buttons: [Review Changes] and [Ignore Warning]. Persistent State: If "Ignore" is clicked, the warning disappears for the current session (or is stored in the record metadata). Additional Context Preventing human error at the interface level will significantly reduce support tickets related to "broken" DNS configurations that are actually just results of accidental duplication.

rdeavila commented

2026-04-09 21:25:43 -03:00

(Migrated from github.com)

Thank you for your report.

Duplicate values in DNS records are often necessary, which is why we cannot simply prohibit users from entering this type of record. The only issue would be a combination of name + value that are exactly the same, but the AWS API already validates that.

Therefore, the most sensible approach is to provide the user with greater visibility of duplicate records, allowing them to see for themselves if what they entered already exists and how the records are duplicated, even across different zones. We added this functionality in v1.1.1 for administrators only, under the Duplicates section. I hope this helps.

Thank you for your report. Duplicate values in DNS records are often necessary, which is why we cannot simply prohibit users from entering this type of record. The only issue would be a combination of **name + value** that are exactly the same, but the AWS API already validates that. Therefore, the most sensible approach is to provide the user with greater visibility of duplicate records, allowing them to see for themselves if what they entered already exists and how the records are duplicated, even across different zones. We added this functionality in [v1.1.1](https://github.com/rda-run/ns116/releases/tag/v1.1.1) for administrators only, under the **Duplicates** section. I hope this helps.

👍 1