-
Notifications
You must be signed in to change notification settings - Fork 652
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
Discovery mode interferes with system DNS configuration #56
Comments
Comment by plietar librespot uses mDNS for zeroconf authentication by default. This may interfere with unusual DNS setups. |
Comment by kcning With this option it doesn't interfere with the DNS setups, but I could't login either. This is the backtrace with librespot built with debug info. I guess the dns issue is solved. I can close this thread and open a new one if you prefer that. It's possibly related to #167
|
Comment by neographikal This looks a bit like the issue I'm experiencing: https://github.com/shanemeagher/service.librespot/issues/3 Doesn't resolve as well, no custom DNS setup btw, just libreelec out of the box and Openwrt on the router (gets results from provider DNS and Google as backup). |
Comment by dowhiletrue I use avahi daemon (zerconf) for several services. Whenever I want to use librespot I have to stop that daemon, which runs on port 5353, first. Does librespot has its own zeroconf functionality which interferes with avahi? |
Comment by shanemeagher @dowhiletrue yes, librespot has mdns / zeroconf built-in. Pull Request #246 allows librespot to be built to use an existing avahi install which should avoid this conflict. Until this is merged, setting |
See #13 for continued discussions |
Issue by kcning
Tuesday Apr 25, 2017 at 11:02 GMT
Originally opened as plietar/librespot#178
Hi, I can't launch librespot because of dns resolve failure. Below is the error msg.
update: backtrace with debug info.
I have dnscrypt and dnsmasq set up. dnsmasq binds to 127.0.0.1:53, which queries dnscrypt in case the address is not known. I have noticed that, when launching librespot,
I can't resolve any address (system-wide).
It seems like all the dns resolves are intercepted by librespot. Is this normal? And is there a way to fix this?
The text was updated successfully, but these errors were encountered: