-
Notifications
You must be signed in to change notification settings - Fork 94
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
quasar is spamming DNS requests for google.com #64
Comments
Got me worried for a second, then remembered I had completely removed the GA tracking, so at least that's not it. But you're right, it's doing a lookup every second here. I don't like that either. |
Sorry for opening the bug in the wrong place, for some reason I was under the impression the daemon wasn't open source (though it appears to be missing a licence still?). Would make more sense to have the connectivity check triggered by a connection timeout, I think. |
It's ok to file most issues here, and yes I'll be looking into changing the connectivity check, or feel free to make a PR on the daemon's repo. |
This issue is identical to steeve#208
I noticed pulsar was sending DNS requests for the
google.com.
A and AAAA records once every second. I removed it and installed plugin.video.quasar 0.9.3 just now, but the problem is still occurring.The threads in the quasar daemon process are doing the
google.com.
lookup followed by connecting a socket to UDP port 9 on one of the addresses returned by the lookup, registering the socket with epoll, then almost immediately closing the socket without sending any traffic.OpenELEC does not cache the DNS results so the lookups might be side effects of regular calls to
net.Dial
. The lookup/connect/close every second seems like strange behaviour, though.The text was updated successfully, but these errors were encountered: