Skip to content
New issue

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

[13.4 stable] App-shared port without DNS server is not necessarily an issue #4345

Merged
merged 1 commit into from
Oct 14, 2024

Conversation

milan-zededa
Copy link
Contributor

Not having DNS servers configured (while link is OK and IP address is assigned), is not necessarily a failure for an app-shared interface. Some applications might not require DNS for external hostnames and may only use internal DNS servers to resolve the names of other apps running on the same device. However, we should still issue a warning about this potential issue.

Signed-off-by: Milan Lenco [email protected]
(cherry picked from commit e7bb230)

Not having DNS servers configured (while link is OK and IP address
is assigned), is not necessarily a failure for an app-shared interface.
Some applications might not require DNS for external hostnames
and may only use internal DNS servers to resolve the names of other apps
running on the same device. However, we should still issue a warning about
this potential issue.

Signed-off-by: Milan Lenco <[email protected]>
(cherry picked from commit e7bb230)
@OhmSpectator OhmSpectator merged commit 5b0077d into lf-edge:13.4-stable Oct 14, 2024
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants