NET-600

[uGiFarukh]

Describe your changes

• When individual extclient dns is changed or removed, it reflects on the UI properly and also gets updated on backend.
• Extclients DNS now properly set from ingress dns value provided that the individual extclient DNS are not present. Updated DNS only applies to newly created extclients after an ingress dns update from the netmaker UI. Individual extclients DNS which are set by user will take precedence over ingress gateway dns.

Related to NET-468 and NET-600

Provide Issue ticket number if applicable/not in title

Provide testing steps

1. Create an ingress gateway with a DNS address set.
2. Create extclients using this ingress gateway.
3. Open the extclient's details page by clicking on the name.
4. This page should reflect the DNS set on the ingress gateway.
5. Change the ingress gateway dns server to a different one and create another extclient.
6. New ingress gateway dns now should be reflected on the new extclient details page.
7. Any ingress gateway dns changes should properly reflect on newly created extclients unless an extclient have dns server set through its own configuration page.
8. Click on edit button of any extclient.
9. Update client DNS field click on update client.
10. Clear client DNS field and click on update client.
11. Extclient dns should be now clearing or changing properly.

Checklist before requesting a review

• My changes affect only 10 files or less.
• I have performed a self-review of my code and tested it.
• If it is a new feature, I have added thorough tests, my code is <= 1450 lines.
• If it is a bugfix, my code is <= 200 lines.
• My functions are <= 80 lines.
• I have had my code reviewed by a peer.
• My unit tests pass locally.
• Netmaker is awesome.

[abhishek9686]

issue related to this ticket is totally different

[Aceix]

i think this should be empty instead