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

Delete norecursion from the dnsServerHandler chain #463

Merged

Conversation

glazychev-art
Copy link
Contributor

A recursive DNS is used to allow one DNS-server communicates with several other DNS servers to find the desired IP address.

In other words, we won't be able to find an external server without this flag (even do apk update)

Signed-off-by: Artem Glazychev artem.glazychev@xored.com

Signed-off-by: Artem Glazychev <artem.glazychev@xored.com>
Copy link
Member

@denis-tingaikin denis-tingaikin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch!

@denis-tingaikin denis-tingaikin merged commit 35d9b9f into networkservicemesh:main Jul 22, 2022
nsmbot pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Jul 22, 2022
…d-nsc@main

PR link: networkservicemesh/cmd-nsc#463

Commit: 35d9b9f
Author: Artem Glazychev
Date: 2022-07-22 17:07:59 +0700
Message:
  - Delete norecursion from the dnsServerHandler chain (#463)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
denis-tingaikin pushed a commit to networkservicemesh/deployments-k8s that referenced this pull request Jul 24, 2022
…d-nsc@main (#6855)

PR link: networkservicemesh/cmd-nsc#463

Commit: 35d9b9f
Author: Artem Glazychev
Date: 2022-07-22 17:07:59 +0700
Message:
  - Delete norecursion from the dnsServerHandler chain (#463)
Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>

Co-authored-by: NSMBot <nsmbot@networkservicmesh.io>
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