Do we need to add the possibility to confgure static DNS entries?

Description

Currently, we support DNSConfigs related to the concrete DNS servers.
https://github.com/networkservicemesh/api/blob/master/pkg/api/networkservice/connectioncontext.proto#L66-L71.

Probably it can be used to add an additional config into https://github.com/networkservicemesh/api/blob/master/pkg/api/networkservice/connectioncontext.proto#L73
That will represent static DNS entry.

message StaticEntry {
    string domain = 1;
    string ip = 2;
}

message DNSContext {
    repeated DNSConfig configs = 1;
  + repeated StaticEntry static_entries = 2;
}

It can be used to configure DNS static entries on the client-side. Probably it is useful for external applications that using DNS domains inside.

Question

Is it make sense?

Start by reading pkg/api/networkservice/connectioncontext.proto around lines 66–73, including DNSConfig and DNSContext. Clarify whether static DNS entries are needed and what schema and compatibility requirements are accepted; the issue is done when the project has a decided API change or a documented decision not to make one.