Created attachment 4078 [details]
squeezecenter log file

SETUP: I have two NICs on my notebook -- a WiFi card (currently active) and an unused 100BaseT. The wired interface is disconnected and disabled (!), but has a static configuration that includes a name server.

BUG #1: Slim::Networking::Async::DNS uses Net::DNS::Resolver to obtain the list of name servers. The latter scans the configuration of all adapters, and picks both the usable NS from WiFi card and unusable one from disabled wired 100BaseT interface. This is clearly a bug on part of Net::DNS::Resolver, but it wouldn't be fatal if not for...

BUG #2: Slim::Networking::Async::DNS runs the check for NS availability. The server obtained from WiFi interface answers ok, and the one from the wired interface doesn't (not a surprise). Based on that, Slim::Networking::Async::DNS not to use any local NS at all and switches automatically to OpenDNS. Using OpenDNS does not work for me, as  my home network is behind a NAT/firewall and has a limited UDP connectivity.

SUGGESTIONS: give priority to using local NS servers, when at least some are available. Switching to OpenDNS upon first fault should not be considered a reliable solution, as in many environments the external NS may be inaccessible.

Please find the log file attached (10.12.68.1 is a working NS, a local WiFi router, and 217.15.16.1 is a dead NS obtained from disabled 100BaseT interface). 

I set the severity to major, as the combination of these two bugs rendered the out-of-box SqueezeCenter unusable on my PC, and I believe the setup that I have is not so uncommon.