Bugzilla – Bug 17917
DNS failures get cached -- resulting in persistent "Couldn't resolve IP address for" errors
Last modified: 2012-03-05 00:25:57 UTC
Every so often, Internet radio and access to mysqueezebox stop working on all my players. (I have 4 "Squeezebox 3"s and one "Squeezebox Boom" connected by a wired network to the Logitech Media Server.) I get the error "Couldn't resolve IP address for: www.mysqueezebox.com" or "Couldn't resolve IP address for: www.bbc.co.uk" both on the player and in the server logs. I have experienced this problem three times now - twice when running LMS on Ubuntu and once when running it on FreeBSD. In all cases, once it has occurred, it persists until LMS is restarted. It took a long time for me to discover this because when you ask Logitech support folks (in forums or a ticket) about any error involving "Couldn't resolve IP address", they immediately assume that something is wrong with your network / firewall / router etc. Message #66 in this forum thread http://forums.logitech.com/t5/MySqueezebox-com-Squeezebox/Cannot-resolve-IP-addresses/m-p/728420 suggests (a little bluntly) that the problem is related to transient DNS failures being cached by LMS. If so, this would seem like an easy fix...
You get.my vote, this is a classic issue the usual explanation is that ss/sc/sbs/LMS is running before the host machine have got a proper network setup from the dhcp or similar . So people fix it by delaying the startup or alter the order of startup . If this is your case you should also find error messages about DNS errors in you fault log. LMS has it own check if DNS is working routine built in for some reason ? The bug part is that the initial condition that causes this is transient and often gone in a matter of seconds after boot of the machine but LMS stubbornly insit that DNS is broken this only checked when LMS starts and never again ? And why this functionality exist in the first place is a mystery ? Why not just trust the OS and let LMS just use the network interface it causes only problems and solves none. If it then fails to communicate write out an error message but as designed now LMS is not even going to try.
please add your information to bug 17571 which is already targeted for next release. *** This bug has been marked as a duplicate of bug 17571 ***