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

Explicit fallthrough is needed while request does not match configured zones #956

Open
juju812 opened this issue Nov 10, 2022 · 7 comments
Labels
bug Something isn't working good first issue Good for newcomers priority:low

Comments

@juju812
Copy link

juju812 commented Nov 10, 2022

While demonstrating #954, I found that explicit fallthrough is needed while request does not match configured zones, and this is different with behavior of kubernetes and multicluster. If fallthrough not configured, NOTZONE will be returned.

I found this change is introduced by 744b666. Could you please kindly clarify if there's any specific consideration, or we can just align the code with kubernetes :

func (lh *Lighthouse) ServeDNS(ctx context.Context, w dns.ResponseWriter, r *dns.Msg) (int, error) {
	...
	// qname: mysvc.default.svc.example.org.
	// zone:  example.org.
	// Matches will return zone in all lower cases
	zone := plugin.Zones(lh.Zones).Matches(qname)
	if zone == "" {
		// implicit fallthrough while request does not match configured zones
		return plugin.NextOrFailure(lh.Name(), lh.Next, ctx, w, r)
	}
       ...
}
@dfarrell07 dfarrell07 added the bug Something isn't working label Nov 15, 2022
@dfarrell07
Copy link
Member

CC @vthapar

@stale
Copy link

stale bot commented May 21, 2023

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label May 21, 2023
@dfarrell07 dfarrell07 removed the wontfix This will not be worked on label May 30, 2023
@stale
Copy link

stale bot commented Oct 15, 2023

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Oct 15, 2023
@skitt skitt removed the wontfix This will not be worked on label Oct 17, 2023
@skitt
Copy link
Member

skitt commented Oct 17, 2023

@vthapar can you take a look at this?

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Oct 24, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 31, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Submariner 0.19 Oct 31, 2024
@tpantelis tpantelis removed the stale label Oct 31, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Backlog Oct 31, 2024
@tpantelis tpantelis reopened this Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers priority:low
Projects
Status: Backlog
Development

No branches or pull requests

5 participants