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

Specific DNS Match Not Prioritized Over General Match #3225

Open
JonathanManass opened this issue Jan 22, 2025 · 0 comments · May be fixed by #3226
Open

Specific DNS Match Not Prioritized Over General Match #3225

JonathanManass opened this issue Jan 22, 2025 · 0 comments · May be fixed by #3226

Comments

@JonathanManass
Copy link

Describe the problem

When Creating two DNS entries it is not using the more precise one.
E.g. I If I nslookup a.example.com it is using the first more general match domain, when I'd like it to use the second.

To Reproduce

  • Create a DNS with match domain example.com
  • Create a second DNS with match domain a.example.com

Expected behavior

I would want it to use the Nameserver of the second DNS if searching for a.example.com and the first for any subdomain other than a
Instead for me it is using the first Nameserver even when searching for a.example.com

Are you using NetBird Cloud?

Self Hosted Version 0.36.3

NetBird version

0.36.3

NetBird status -dA output:

It does show both DNS entries like

Nameservers:
[x:53, x:53] for [example.com] is Available
[x:53] for [a.example.com] is Available

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants