PaulinPosset wrote:
>
> EDIT:
>
> As they say: "Google is your friend." It might be unrelated but there
> appear to have been issues in the past with LMS caching all DNS requests
> even failed ones. So presumably because HLS requires constant lookups,
> when one does fail LMS will try and use the failed DNS until the stream
> data runs out? With the old way once a stream was connected no more DNS
> lookups were needed and the stream just played. Or am I barking up the
> wrong tree?
It doesn't look like it tries to cache failed lookups. I'm not sure what
it would put in the cache...
Yes, as I understand it with old style streaming, there is one stream
connection that is maintained with the server, requiring only one DNS
lookup when it starts.
If you are able to find a way to modify the perl in windows LMS, you
could try the following hack in Slim/Networking/Async/DNS.pm. At around
line 74 add the lines in red:
Code:
--------------------
my $addr = $res->[3];
my $ttl = $res->[4];
# Hacked to force ttl to 30 minutes.
if ($ttl < 1800) { $ttl = 1800; }
main::DEBUGLOG && $log->is_debug && $log->debug( "Got DNS
response $addr for $host (ttl $ttl)" );
--------------------
That will force the time-to-live of all DNS responses to 30 minutes, so
it is possible that it could break some things - but I think most
servers are pretty static.
------------------------------------------------------------------------
utgg's Profile: http://forums.slimdevices.com/member.php?userid=40900
View this thread: http://forums.slimdevices.com/showthread.php?t=53229
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
