-
-
Notifications
You must be signed in to change notification settings - Fork 592
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
[BUG] Linux Client can not set DNS with custom port #3443
Comments
@0xF61, what's your Linux distro/version/kernel? Can you share the log please?
(run your query in this 1 minute time frame) This should be handled already, unless something went wrong |
Hello @lixmal thank you for your quick response. I ran it for 10sec and ran dig with and without specifying port. The debug helped me to see this error. You can see the all WARN's lines on logs in this SS. ( I use systemd-resolved service on my machine ) I'm running arch with latest kernel. |
You mentioned using systemd-resolved, yet the log discovered a plain file:
can you show the content of |
What you mentioned Should I also configure the resolved.conf to match my dns record? I also searched that but couldn't find a solution to set custom port to dns server on systemd-resolved. |
Describe the problem
Hello, we are using Netbird to access our assets. We self-hosting everything btw. We assumed that it would not be too much of a problem to change DNS port 53 to 531. This leads us to no problem on Windows, Android, iOS, and macOS clients. Unfortunately, I assume there is an unhandled situation here on Linux clients. First of all,
Netbird up
perfectly sets up the IP which has to be set by Netbird but there is a small issue that it can not set it from 53 to 531. I assume this is not handled on systemd-resolved and netbird client does not cover it.To Reproduce
Steps to reproduce the behavior:
dig a internal.netbird
anddig -p 531 a internal.netbird
address.Expected behavior
I believe it should resolve the domains even DNS port is differ from 53.
Are you using NetBird Cloud?
No we are using selfhosted version of netbird.
NetBird version
0.37.1
NetBird status -dA output:
If applicable, add the `netbird status -dA' command output.
Do you face any (non-mobile) client issues?
No we don't have any issues on mobile clients.
Screenshots
As you can see the port is set to 531.
When it asked on 531 port it works.
Additional context
We have no problem on any other device but only Linux client has this issue.
I solved the issue on my side with below this command btw:
I open this issue and share my solution if no solution can be provided by netbird.
The text was updated successfully, but these errors were encountered: