-
Notifications
You must be signed in to change notification settings - Fork 988
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:Nebula cannot obtain the correct dns server address from the system #909
Comments
Hi @aa51513 - Allowing configuration of a DNS resolver in the config file sounds like a good idea to me. That being said, I'm unsure why the settings in
However, we disable CGO for Nebula builds so I suspect that only the pure Go resolver is in use. If that's the case, and the comment above is correct, I am surprised to hear that your |
Hi @aa51513, are you able to provide the request information? Thanks! |
I'm sorry that I didn't reply in time these days because of some personal matters. |
I am also having a lot of DNS issues. On Linux, I sometimes get a long delay before the connection initiates. After around 30 seconds, I will get an error:
Sometimes it will then just sit there disconnected, although more often than not there will be another message saying the On other occasions (also Linux) it connects ok, but then intermittently and consistently there will be looping error messages:
On Mac I haven't been able to connect at all, but my Mac is such a mix of different interfaces and experiments it's been really difficult to debug. If I run Nebula in a Docker container on the same system though, it performs the same as above. The IP and URL that I removed from above are all standard ipv4 (although there is an ipv6 option on there, the IP in Nebula logs is the ipv4 one) and a subdomain. Domain has been active for months so has propagated fully. Being able to specify DNS servers would be a good step. |
Still trying to explore this. I can replicate it by changing the DNS entries in resolv.conf on my Mac and see it when using a slow connection. Connecting to a VPN changes resolv.conf and also helps replicate this. After the DNS change on occasion it reports:
Then eventually:
and then after another 30 seconds it connects. I see there is a retry cadence: https://github.com/slackhq/nebula/pull/879/files I haven't delved in to the criteria for I also wonder if the timeout of |
This comment was marked as off-topic.
This comment was marked as off-topic.
@maggie44 The error you are seeing is different from the error in the original ticket. Have you tried increasing |
i have a peculiar case where it only fails on system startup |
What version of
nebula
are you using?1.7.2
What operating system are you using?
Linux ( Arm64 )
Describe the Bug
When starting nebula, an error is reported:
ERRO[0000] DNS resolution failed for static_map host error="lookup mynebula.server.com on [::1]:53: read udp [::1]:39679->[:: 1]:53: read: connection refused "hostname=mynebula.server.com network=ip4
It looks like it can't get the correct dns server address from the system, but I type dig command and everything is normal:
As a supplement, the following are the contents of the file
/etc/resolv.conf
on my server:I am very confused, why Nebula uses
[::1]:53
as the address of the dns server, regardless of the system configurationPlease evaluate whether the optional configuration item of dns server address should be added to the configuration file
Logs from affected hosts
ERRO[0000] DNS resolution failed for static_map host error="lookup mynebula.server.com on [::1]:53: read udp [::1]:39679->[:: 1]:53: read: connection refused "hostname=mynebula.server.com network=ip4
Config files from affected hosts
The text was updated successfully, but these errors were encountered: