We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
Is it make sense?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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.
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?
The text was updated successfully, but these errors were encountered: