Project

General

Profile

Actions

Bug #23005

open

Inconsistencies in “DNS settings” directive

Added by Michel BOUISSOU over 1 year ago. Updated 6 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
52
Name check:
To do
Fix check:
To do
Regression:
No

Description

The are some inconsistencies in the “DNS settings” system technique :

- When creating a new directive from this technique, it shows up with both “Nameservers” and “Search suffix” sections open, and the “Options settings” section closed.
- Although the search entry is optional as well as the “options”...

- The displayed options come with a [Delete “blah” #1] button, but this button doen't work as long as there is only one entry, leading to the idea that at least one entry is mandatory (where it isn't i.e. for “search” and ”options”).

- The checkboxes on each section to “enforce” the settings are confusing. Why would we want to list entries that we wouldn't want to apply ? The use of the “enforce” term is even more confusing because it might lead to thinking that will will be “enforced” even though the directive would be in “audit” mode, which is probably not the case.

I suggest that the checkbox be removed, and the technique should not pre-populate its section with sample entries.

i.e. What should I dot if I don't want any “search entry” ? I can't delete it, so should I empty the given sample ? Should I just not check the box that would ”enforce” it ? But if I want to enforce the absence of a “search” entry, how can I achieve this ?


Files

Technique_DNS_settings.png (75.8 KB) Technique_DNS_settings.png Michel BOUISSOU, 2023-07-04 16:40
Actions #1

Updated by Alexis Mousset over 1 year ago

  • Category changed from System techniques to Techniques
Actions #2

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.3.4 to 7.3.5
Actions #3

Updated by Alexis Mousset over 1 year ago

  • Target version changed from 7.3.5 to 7.3.6
Actions #4

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.3.6 to 7.3.7
  • Priority changed from 62 to 61
Actions #5

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.3.7 to 7.3.8
Actions #6

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.8 to 7.3.9
  • Priority changed from 61 to 60
Actions #7

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.9 to 7.3.10
  • Priority changed from 60 to 59
Actions #8

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.10 to 7.3.11
  • Priority changed from 59 to 58
Actions #9

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 7.3.11 to 7.3.12
  • Priority changed from 58 to 57
Actions #10

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.3.12 to 7.3.13
  • Priority changed from 57 to 56
Actions #11

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.3.13 to 7.3.14
  • Priority changed from 56 to 55
Actions #12

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 7.3.14 to 7.3.15
  • Priority changed from 55 to 54
Actions #13

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 7.3.15 to 7.3.16
  • Priority changed from 54 to 53
Actions #14

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.16 to 7.3.17
  • Priority changed from 53 to 52
Actions

Also available in: Atom PDF