Search Domains should not be configured if there is no primary DNS configured.

[liranmauda]

Environment info

• Version: 1.6.1-d4a7fb7
• Deployment: AZURE
• Customer: QA

Actual behavior

1. when there is no primary DNS we are able to configure Search Domains
2. when we are in the process of update restart in the DNS menu the fields are not locked
3. we are missing tool tip on the Search Domains in DNS menu.

Expected behavior

1. Search Domains should not be configured if there is no primary DNS configured.
2. when we are in the process of update restart in the DNS menu the fields should be locked
3. we should add tool tip in the Search Domains in DNS menu.

Nimrod & Shiri saw the bug.

[nimrod-becker]

tooltip text:
“If configured, search domains will be added to the fully qualified domain names when trying to resolve host names”

[nimrod-becker]

@shirimordechay please define the desired behavior of the validations

[shirimordechay]

"when we are in the process of update restart in the DNS menu the fields should be locked" @liranmauda @nb-ohad this looks like a UI bug: when Updating is in process we usually lock the screen (disable all fields).

Regarding the rest, fixed behavior updated on mock:
https://invis.io/YC8MYFMV6#/202360470_Server_DNS_Settings_From_Config

[nimrod-becker]

@shirimordechay what happens when values are entered as secondary and search and then primary value is deleted ?

[shirimordechay]

@nimrod-becker You mean before or after clicking on "save"?

[nimrod-becker]

@shirimordechay Before, Let's say I enter primary, secondary and search and then delete the value in primary